Skip site navigation (1) Skip section navigation (2)

Re: postmaster.pid

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <mha(at)sollentuna(dot)net>
Cc: <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <dpage(at)vale-housing(dot)co(dot)uk>,<pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: postmaster.pid
Date: 2004-08-25 14:25:45
Message-ID: 4842.162.39.122.234.1093443945.squirrel@www.dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
Magnus Hagander said:
>> > 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. :-)
>

[away from my desk so can't check right now] What do we get back down the
pipe? Unless it's something that identifies that we are talking to a
postmaster will we be further advanced than the Unix case? (I agree that
talking on the pipe would be more robust than the simple OpenProcess()
test, regardless of this point).

cheers

andrew




In response to

pgsql-hackers-win32 by date

Next:From: Joerg HessdoerferDate: 2004-08-25 16:24:45
Subject: Re: postmaster.pid
Previous:From: Magnus HaganderDate: 2004-08-25 14:21:32
Subject: Re: postmaster.pid

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group