Re: [8.0.0] out of memory on large UPDATE

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

On Thu, 11 Aug 2005, Tom Lane wrote:

> "Marc G. Fournier" <scrappy(at)postgresql(dot)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(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-08-11 18:20:39 Re: [8.0.0] out of memory on large UPDATE
Previous Message Tom Lane 2005-08-11 17:27:23 Re: [8.0.0] out of memory on large UPDATE