| 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-11 18:20:39 |
| Message-ID: | 29700.1123784439@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:
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aaron Harsh | 2005-08-11 20:41:01 | Re: BUG #1800: "unexpected chunk number" during pg_dump |
| Previous Message | Marc G. Fournier | 2005-08-11 17:55:37 | Re: [8.0.0] out of memory on large UPDATE |