From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to simulate crashes of PostgreSQL? |
Date: | 2009-08-26 15:30:34 |
Message-ID: | 2968dfd60908260830l2fa9807cx9233bac71f6f1ee1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 25, 2009 at 4:55 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I've always thought that the fd.c layer is more about not having to
> configure the code explicitly for max-files-per-process limits. Once
> you get into ENFILE conditions, even if Postgres manages to stay up,
> everything else on the box is going to start falling over. So the
> sysadmin is likely to have to resort to a reboot anyway.
In my case, all sorts of processes were complaining about being unable
to open files. Once Pg panicked and closed all its files, everything
came back to normal. I didn't have to reboot because most everything
was written to retry and/or restart itself, and nothing critical like
sshd croaked.
I think we'll be adding a nagios check to track maxfiles vs. openfiles
from the kernel and alarm when they get close.
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2009-08-26 16:05:36 | Re: best practise/pattern for large OR / LIKE searches |
Previous Message | Tom Lane | 2009-08-26 15:21:42 | Re: Tagged types module and varlena changes |