RE: [HACKERS] backend freezeing on win32 fixed (I hope ;-) ) - Mailing list pgsql-hackers

From Horak Daniel
Subject RE: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
Date
Msg-id 2E7F82FAC1FCD2118E1500A024B3BF907DED3F@exchange.mmp.plzen-city.cz
Whole thread Raw
Responses Re: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
Re: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
RE: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
List pgsql-hackers
> In any case, when one backend quits and another one is 
> started, the new
> one will re-use the semaphore no longer used by the defunct backend.

I have tested my solution a bit more and I have to say that reusing a
semaphore by a new backend works OK. But it is not possible for a newly
created backend to use a semaphore allocated by postmaster (it freezes on
test if the semaphore with given key already exists - done with
semId=semget(semKey, 0, 0) in function IpcSemaphoreCreate() in
storage/ipc/ipc.c ). Why it is, I don't know, but it seems that my solution
uses the ipc library in the right way. There are no longer any error
messages from the ipc library when running the server. And I can't say that
the ipc library is a 100% correct implementation of SysV IPC, it is probably
(sure ;-) )caused by the Windows internals.
        Dan


pgsql-hackers by date:

Previous
From: Vince Vielhaber
Date:
Subject: Re: [HACKERS] Re: [CORE] Re: tomorrow
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Re: [CORE] Re: tomorrow