Re: Really out of memory?

On Tue, 2 Jun 2009, John R Pierce wrote:

> Ben Chobot wrote:
>>  May 31 02:59:40 sfmelwss postgres[30103]: [1-1] ERROR:  out of memory
>>  May 31 02:59:40 sfmelwss postgres[30103]: [1-2] DETAIL:  Failed on request of size 16777212.
>
> Thats a 16MB request  is that your work_mem size or something by any chance?

work_mem is 1MB, but maintenance_work_mem is 16MB. So it's probably
autovacuum kicking off most of these messages.

>>  02:30:01 AM kbmemfree kbmemused  %memused kbbuffers  kbcached kbswpfree
>>  kbswpused  %swpused  kbswpcad
>>  02:40:01 AM     13332   1003316     98.69    130448    198188   1034572
>>  13996      1.33        32
>
> so you only have 13MB memory free.  you have -do- have free swap, however.
>
>
> hey, is any ULIMIT in effect for the postgres process?

Not that I can tell. There's nothing special in /etc/init.d/postgresql or
/etc/sysconfig/pgsql/postgresql, and ulimit -a shows:

core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
max nice                        (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 16127
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
max rt priority                 (-r) 0
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 16127
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

Is there a way to see what the limits are for a given pid? I don't see
anything obviously relevant in /proc/<pid>/....