| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Doug McNaught <doug(at)wireboard(dot)com> | 
| Cc: | Eric Cholet <cholet(at)logilune(dot)com>, pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Memory exhausted in AllocSetReAlloc | 
| Date: | 2001-11-14 15:37:21 | 
| Message-ID: | 6568.1005752241@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
Doug McNaught <doug(at)wireboard(dot)com> writes:
> Have you double checked to make sure the ulimits for postmaster are
> large enough?
More to the point, what have you got SORT_MEM set to?  We're assuming
that this allocation request is correct, and indeed it probably is if
you've got SORT_MEM cranked up to the moon.  But if you don't then
there may be a different issue (like corrupted data).
FWIW, running with SORT_MEM set in the hundreds of megs on a 2gig
box does not strike me as a good idea.  Keep in mind that that number
is *per sorting operation*.  Each backend might be trying to use that
much simultaneously --- in fact, in complex queries it's not hard to
cause a single backend to be executing multiple sort steps.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lincoln Yeoh | 2001-11-14 15:55:57 | Re: Vacuuming - how often? | 
| Previous Message | Steve Brett | 2001-11-14 15:21:36 | Idle in transaction ???? |