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

From: Horak Daniel <horak(at)mmp(dot)plzen-city(dot)cz>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
Date: 1999-08-17 12:06:26
Message-ID: 2E7F82FAC1FCD2118E1500A024B3BF907DED3F@exchange.mmp.plzen-city.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1999-08-17 12:21:19 Re: [HACKERS] Re: [CORE] Re: tomorrow
Previous Message Vince Vielhaber 1999-08-17 11:28:10 Re: [HACKERS] Re: [CORE] Re: tomorrow