| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Cc: | <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: postmaster.pid |
| Date: | 2004-08-25 07:54:43 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE475B1E@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
> > I think it's better to call uor named pipe. That way we'll
> find out if
> > it's actually a postmaster of ours or a different process
> alltogether
> > there.
>
> I'm not sure that's a good idea. The function is there to
> emulate the unix kill() which doesn't care what the process
> is. Changing the code as you suggest could cause confusionon
> Windows if someone uses kill() for other purposes.
Why would they link with libpgport if they use it for other purposes?
;-)
But sure, we don't really care if it's a postmaster. Then OpenProcess()
is probably the best way, yes.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2004-08-25 07:56:05 | Re: postmaster.pid |
| Previous Message | Dave Page | 2004-08-25 07:51:25 | Re: postmaster.pid |