Re: BUG #3242: FATAL: could not unlock semaphore: error code 298 - Mailing list pgsql-bugs

From Marcin Waldowski
Subject Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date
Msg-id 462DAD54.2040008@sulechow.net
Whole thread Raw
In response to Re: BUG #3242: FATAL: could not unlock semaphore: error code 298  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
List pgsql-bugs
Tom Lane wrote:
> Marcin Waldowski <M.Waldowski@sulechow.net> writes:
>
>> Ok, that's the end of the story :) My workmate has confirmed that during
>> night test PostgreSQL worked perfectly :)
>>
>
> That fix was Obviously Necessary even without testing -- you're being
> too conservative about not applying it, Magnus.
>
>             regards, tom lane
>

I was thinking that this fix will be included in 8.2.4 :) Now I know
that it's too late (8.2.4 is released). Now I trying to find what
conditions causes to realease new version of PostgreSQL (with fixes).
Does any document exist about that?

I just need to know when can I expect 8.2.5 with this fix
(approximately) :/ Thanks in advance.

Regards, Marcin

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Next
From: Tom Lane
Date:
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298