From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SIGUSR1 pingpong between master na autovacum launcher causes crash |
Date: | 2009-08-24 16:28:21 |
Message-ID: | 14167.1251131301@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Zdenek Kotala wrote:
>> Just a confirmation that Alvaro's patch+ReleasePostmasterChildSlot() fix
>> solves the problem and PostgreSQL survives well during a memory
>> shortages.
> So this patch would do it.
Looks good to me, but I think you should also increase the avlauncher
delay from 100ms -> 1s as Zdenek suggested.
> I think this stuff about postmaster child slots is later than
> launcher/worker split. I don't recall seeing it before.
Yeah, I added that recently to try to detect postmaster children
that exit without cleaning up properly. I seem to have missed this
error case :-(. Actually it looks like fork failure for regular
backends gets it wrong too :-( :-( --- would you please also add one
in the pid<0 path in BackendStartup? I think this logic is in 8.4
too, in which case it'll need to be back-patched.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-08-24 16:28:38 | Re: hba load error and silent mode |
Previous Message | Christopher Browne | 2009-08-24 16:24:15 | Re: 8.5 release timetable, again |