| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Vick Khera <vivek(at)khera(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Out of memory condition |
| Date: | 2014-12-11 20:46:18 |
| Message-ID: | 29097.1418330778@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> writes:
> Extracted ulimits values from postmaster pid and they look as expected:
> [root(at)00002-NfseNet ~]# cat /proc/2992/limits
> Limit Soft Limit Hard Limit
> Units
> Max address space 1024000000 unlimited
> bytes
So you've got a limit of 1GB on process address space ... that's
probably why it's burping on allocations of a couple hundred meg,
especially if you have a reasonably large shared_buffers setting.
You might as well be running a 32-bit build (in fact, a 32-bit
build could still do a lot better than that).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert DiFalco | 2014-12-11 20:52:37 | Re: Help Optimizing a Summary Query |
| Previous Message | Scott Marlowe | 2014-12-11 20:43:05 | Re: Out of memory condition |