From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Anita Lederer" <anita(dot)lederer(at)googlemail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: out of memory |
Date: | 2006-08-15 20:48:37 |
Message-ID: | 20196.1155674917@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Anita Lederer" <anita(dot)lederer(at)googlemail(dot)com> writes:
> i have a statement which ends with
> ERROR: out of memory
> DETAIL: Failed on request of size 639.
Do you have work_mem set to a large value? Your query plan contains
several sorts so would potentially try to use several times work_mem
... if that's more than the kernel will allow one process to have,
you would get a failure like this.
The other theory that comes to mind is that you've discovered an
intraquery memory-leak bug, but there's not nearly enough information
here to find it if so.
The out-of-memory error should result in dumping a list of memory
context statistics into the postmaster's log file --- if you can post
that information it would be helpful.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2006-08-16 00:52:25 | Re: BUG #2576: tcp_keepalive doesn't work |
Previous Message | tomas | 2006-08-15 16:49:37 | Re: BUG #2577: Notice: Only variable references should be retur.. |