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

From Magnus Hagander
Subject Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date
Msg-id 462CE286.2000101@hagander.net
Whole thread Raw
In response to Re: BUG #3242: FATAL: could not unlock semaphore: error code 298  (Marcin Waldowski <M.Waldowski@sulechow.net>)
List pgsql-bugs
Marcin Waldowski wrote:
>
>> The following bug has been logged online:
>>
>> Bug reference:      3242
>> Logged by:          Marcin Waldowski
>> Email address:      M.Waldowski@sulechow.net
>> PostgreSQL version: 8.2.3 and 8.2.1
>> Operating system:   Windows XP SP2
>> Description:        FATAL: could not unlock semaphore: error code 298
>> Details:
>
> Magnus,
>
> I have applied your patch on 8.2.3 source and built it in mingw
> environment (with default settings). After 3 hours of performance test
> nothing happened, log is clear :) In previous test error occur always
> within first hour (most often within first 20 minutes), so I can
> initialy confirm that this fix works. We will also leave test running
> for the night to be absolutely sure that it's ok. I will inform you
> about the result.

Great!

I'll await your confirmation tomorrow before applying the patch.

//Magnus

pgsql-bugs by date:

Previous
From: "Dorochevsky,Michel"
Date:
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b ject
Next
From: Tom Lane
Date:
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b ject