RE: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
Horak Daniel <horak@mmp.plzen-city.cz>
From: Horak Daniel <horak@mmp.plzen-city.cz>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>
Cc: "'pgsql-hackers@postgreSQL.org'" <pgsql-hackers@postgreSQL.org>
Date: 1999-08-17T12:06:26Z
Lists: 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