Re: [8.0.0] out of memory on large UPDATE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [8.0.0] out of memory on large UPDATE
Date: 2005-08-12 02:22:58
Message-ID: 12802.1123813378@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Marc G. Fournier" <scrappy(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2005-08-12 02:34:15 Re: Cascading updates run seperately
Previous Message Marc G. Fournier 2005-08-12 02:18:31 Re: [8.0.0] out of memory on large UPDATE