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

From Marc G. Fournier
Subject Re: [8.0.0] out of memory on large UPDATE
Date
Msg-id 20050811145448.X1002@ganymede.hub.org
Whole thread Raw
In response to [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  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [8.0.0] out of memory on large UPDATE  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-bugs
On Thu, 11 Aug 2005, Tom Lane wrote:

> "Marc G. Fournier" <scrappy@postgresql.org> writes:
>> On Thu, 11 Aug 2005, Tom Lane wrote:
>>> If you've got any AFTER UPDATE triggers on that table, you could be
>>> running out of memory for the pending-triggers list.
>
>> Nope, only have a BEFORE UPDATE, or would that be similar except for at
>> which point it runs out of memory?
>
> Nope, BEFORE UPDATE shouldn't result in any permanent memory
> accumulation.
>
> An out-of-memory error should result in a long report in the postmaster
> log about how many bytes in each memory context --- can you post that?

This is all I'm seeing in the logs:

# grep "\[653\]" pgsql
Aug 11 08:45:47 pgsql80 pg[653]: [34-1] ERROR:  out of memory
Aug 11 08:45:47 pgsql80 pg[653]: [34-2] DETAIL:  Failed on request of size 32.



----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #1800: "unexpected chunk number" during pg_dump
Next
From: Tom Lane
Date:
Subject: Re: [8.0.0] out of memory on large UPDATE