From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Horak Daniel <horak(at)mmp(dot)plzen-city(dot)cz>, "'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 15:01:45 |
Message-ID: | 199908171501.LAA08905@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Horak Daniel <horak(at)mmp(dot)plzen-city(dot)cz> writes:
> > 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.
>
> It seems that you have found a bug in the cygipc library. I suggest
> reporting it to the author of same...
Yes, but can we expect all NT sites to get the patch before using
PostgreSQL? Is there a workaround we can implement?
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Herouth Maoz | 1999-08-17 15:24:26 | RE: [SQL] datediff function |
Previous Message | Bruce Momjian | 1999-08-17 15:00:03 | Re: [HACKERS] Re: [CORE] Re: tomorrow |