Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298
Дата
Msg-id 20070420075110.GA9033@svr2.hagander.net
обсуждение исходный текст
Ответы Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298  (Marcin Waldowski <M.Waldowski@sulechow.net>)
Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Fri, Apr 20, 2007 at 09:20:05AM +0200, Marcin Waldowski wrote:
> Hello.
> 
> I've made some analysis of PostgreSQL code. It looks like void 
> PGSemaphoreUnlock(PGSemaphore sema) from backend\port\win32_sema.c was 
> executed one time more than needed.

Certainly looks that way.

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?)

//Magnus



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Zoltan Boszormenyi
Дата:
Сообщение: Re: parser dilemma
Следующее
От: Marcin Waldowski
Дата:
Сообщение: Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298