From: | Paul Warren <pw(at)researchresearch(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | pg_dump being killed by oom killer |
Date: | 2013-10-29 12:17:48 |
Message-ID: | CALn4Y7F63-f7bPqROs0xYXoQZkdoxaCduymhjhffh3VWcL1nOA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I'm to the lists so bare with me please.
I have a vm running debian 6 with linux kernel 2.6.32-11-pve, when i run
pg_dump -Fc -U postgres db name > db name.dump
after so long the process is killed, when I look in the /var/log/kern.log i
see the following entry
Oct 29 12:07:14 www1 kernel: OOM killed process 0 (pg_dump) vm:5269904kB,
rss:5210224kB, swap:0kB
The vm has 16 cpu's and is using around 10%, when I run pg_dump it goes up
by 3 / 5 % so not using alot of cpu usage. IT has 30gb of ram and 1gb of
swap, the system uses around 2mb of swap and 15gb of ram, when pg_dump runs
the swap doesn't move but the ram goes up by 3 / 4 gb before the process is
killed.
The machine had only 20gb of ram so I've increased the ram usage and still
get the same issue. if I run pg_dump on any other db it works fine, if we
run a pg_dump script by table on the failing database it works fine.
The backup is going directly to a nas device which has 1.2 tb free. The vm
has aroudn 40gb free as well.
Any ideas what this could be? it seems to be a memory issue but I can't
seem to see what / why it's happening.
oh the DB is around 1.5 gb / 2gb in size
Thanks
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Klochkov | 2013-10-29 13:01:44 | Re: pg_dump being killed by oom killer |
Previous Message | David Johnston | 2013-10-29 03:56:29 | Re: Sequences vs statistics |