Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298
От | Tom Lane |
---|---|
Тема | Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298 |
Дата | |
Msg-id | 29400.1177081115@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298 (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code
298
|
Список | pgsql-hackers |
Magnus Hagander <magnus@hagander.net> writes: > On Fri, Apr 20, 2007 at 09:20:05AM +0200, Marcin Waldowski wrote: >>> I've looked at the code there, and can't find a clear problem. One way it >>> could happen is if the actual PGSemaphoreUnlock() is called once more than >>> needed. > CC:ing to hackers for this question: > Any chance that's happening? If this happens with SysV semaphores, will > they error out, or just say it was done and do nothing? (meaning should we > actuallyi be ignoring this error on windows?) How is it possible for a semaphore to be unlocked "too many times"? It's supposed to be a running counter of the net V's minus P's, and yes it had better be able to count higher than one. Have we chosen the wrong Windows primitive to implement this? regards, tom lane
В списке pgsql-hackers по дате отправления: