Re: postmaster.pid

> > But sure, we don't really care if it's a postmaster. Then 
> > OpenProcess() is probably the best way, yes.
> 
> Au contraire!!  One of the problems with the Unix 
> implementation is that you *can't* tell for sure if the 
> target process is a postmaster.  See past discussions about 
> how startup occasionally fails because we get fooled by the 
> PID mentioned in postmaster.pid now belonging to pg_ctl or 
> some other Postgres-owned process.
> 
> This is a place where the Windows version can actually be 
> better than the Unix one.  Please fix it and stop imagining 
> that your charter is to duplicate a particular Unix syscall 
> bug-for-bug.

Ok, if you say so :-) I had the general impression we wanted that. But
then let's go with the
send-signal-0-down-the-pipe-and-ignore-it-in-the-backend. :-)

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faqs/FAQ.html