Postgres Pro
Downloads
Home   >   mailing lists

Re: [8.0.0] out of memory on large UPDATE - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [8.0.0] out of memory on large UPDATE
Date
Msg-id 12802.1123813378@sss.pgh.pa.us
Whole thread Raw
In response to Re: [8.0.0] out of memory on large UPDATE  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: [8.0.0] out of memory on large UPDATE  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-bugs
Tree view 
"Marc G. Fournier" <scrappy@postgresql.org> writes:
> 'k, does this help any?

> TopMemoryContext: 40960 total in 4 blocks; 8632 free (10 chunks); 32328 used
> SPI Plan: 3072 total in 2 blocks; 1728 free (0 chunks); 1344 used
> TopTransactionContext: 534765568 total in 74 blocks; 2144 free (68 chunks); 534763424 used

Yeah, the leak is clearly in TopTransactionContext.  That doesn't let
the trigger code off the hook though, because the pending-triggers list
is kept there.  Are you *sure* there are no AFTER triggers here?
(Don't forget foreign-key checking triggers.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: [8.0.0] out of memory on large UPDATE
Next
From: Stephan Szabo
Date:
Subject: Re: Cascading updates run seperately