Re: [PATCHES] postmaster.pid
- From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, <pgsql-hackers-win32(at)postgresql(dot)org>, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
- Subject: Re: [PATCHES] postmaster.pid
- Date: Thu, 26 Aug 2004 17:11:48 +0100
- Message-id: <E7F85A1B5FF8D44C8A1AF6885BC9A0E41A78DC(at)ratbert(dot)vale-housing(dot)co(dot)uk>
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 26 August 2004 16:24
> To: Dave Page
> Cc: Andrew Dunstan; Magnus Hagander;
> pgsql-hackers-win32(at)postgresql(dot)org; PostgreSQL-patches
> Subject: Re: [PATCHES] [pgsql-hackers-win32] postmaster.pid
>
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> >> ISTM we should not ever queue any event for signal 0.
>
> > That was my original intention, however Magnus thought it
> best just to
> > let it be queued and subsequently ignored by the backend - thinking
> > about it 15 minutes later I can't for the life of me think
> why that's
> > any better...
>
> Are there any error cases that we would miss detecting if it
> didn't go that far?
None that I can think of. If we managed to open the pipe and get the
zero back, then we've proved the process is there and is postgres.
Regards Dave.
Home |
Main Index |
Thread Index