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

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Horak Daniel <horak(at)mmp(dot)plzen-city(dot)cz>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'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 14:41:28
Message-ID: 199908171441.KAA08651@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[Charset iso-8859-1 unsupported, filtering to ASCII...]
> > 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.

Seems we may have to use the patch, or make some other patch for NT-only
that works around this NT bug.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-08-17 14:42:45 Re: [HACKERS] Re: [CORE] Re: tomorrow
Previous Message Thomas Lockhart 1999-08-17 14:40:45 Re: [HACKERS] Query string lengths