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 29700.1123784439@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>)
List pgsql-bugs
"Marc G. Fournier" <scrappy@postgresql.org> writes:
> On Thu, 11 Aug 2005, Tom Lane wrote:
>> 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.

(looks at code...)  Hmm, it seems to print the report on stderr.  I
imagine we did that because there's possibly not enough memory to use
elog.  Anyway, can you arrange to capture the postmaster's stderr and
try it again?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [8.0.0] out of memory on large UPDATE
Next
From: Allan Wang
Date:
Subject: Cascading updates run seperately