Re: BUG #8578: loading a 33G (compressed) pg_dump into a fresh host and db instance crashes a postgresql process

From: Robert Nix <robert(at)urban4m(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8578: loading a 33G (compressed) pg_dump into a fresh host and db instance crashes a postgresql process
Date: 2013-11-06 01:46:35
Message-ID: CAC2EkfPQ3PE4Zgo3Y9zD0cjaKVyCxcmZeLOZ6qy30kPhaep5dQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks for the quick response, Tom. Sure enough. I found the OOM message in
syslog. And thanks for the link. I'll try those suggestions. Just out of
curiosity, will using psql -f alter the behavior, in this case, with
respect to memory?
Thanks again

On Tue, Nov 5, 2013 at 8:11 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> robert(at)urban4m(dot)com writes:
> > 2013-11-05 17:04:21 EST LOG: server process (PID 5869) was terminated by
> > signal 9: Killed
>
> OOM killer, almost certainly. Check your kernel log to confirm.
> Then read about preventing OOM kills:
>
> http://www.postgresql.org/docs/9.3/static/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT
>
> regards, tom lane
>

--
.nix

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-11-06 02:20:24 Re: BUG #8578: loading a 33G (compressed) pg_dump into a fresh host and db instance crashes a postgresql process
Previous Message Tom Lane 2013-11-06 01:11:44 Re: BUG #8578: loading a 33G (compressed) pg_dump into a fresh host and db instance crashes a postgresql process