>
>
> > ...
> > AfterTriggerEvents: 2642403328 total in 327 blocks; 10176 free (319
> > chunks); 2642393152 used
>
> And there's the problem. Evidently you have an AFTER trigger on the
> table, and the queued events for that trigger are overrunning memory.
>
That's interesting - I don't know
> > I need to populate a new column in a Postgres 8.3 table. The SQL would be
> something like "update t set col_c = col_a + col_b". Unfortunately, this
> table has 110 million rows, so running that query runs out of memory.
>
> That's unusual, what is the error you get?
Here it is:
TopMemoryCont
Hi,
I need to populate a new column in a Postgres 8.3 table. The SQL would be
something like "update t set col_c = col_a + col_b". Unfortunately, this
table has 110 million rows, so running that query runs out of memory.
In Oracle, I'd turn auto-commit off and write a pl/sql procedure that keeps
a
--(end of broadcast)---
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
>match
>
--
Len Walter [EMAIL PROTECTED] http://crookedtimbre
hat should be disconnected, then sending them TERM
or QUIT signals, but TERM has no effect and QUIT puts the whole
database into recovery mode.
Thanks in advance,
Len
--
Len Walter [EMAIL PROTECTED] http://crookedtimbre.net
---(end of broadcast)-
