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

From: Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, magnus(at)hagander(dot)net
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date: 2007-04-24 07:10:12
Message-ID: 462DAD54.2040008@sulechow.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Tom Lane wrote:
> Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-04-24 07:38:47 Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Previous Message Tom Lane 2007-04-24 06:25:41 Re: BUG #3242: FATAL: could not unlock semaphore: error code 298

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroki Kataoka 2007-04-24 07:22:39 Re: Dead Space Map version 3 (simplified)
Previous Message Tom Lane 2007-04-24 06:25:41 Re: BUG #3242: FATAL: could not unlock semaphore: error code 298