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 462C7F7C.2020900@sulechow.net
Whole thread Raw
In response to BUG #3242: FATAL: could not unlock semaphore: error code 298  ("Marcin Waldowski" <M.Waldowski@sulechow.net>)
Responses Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
List pgsql-bugs
> 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.

Thanks again, Marcin

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3244: problem with PREPARE
Next
From: "Dorochevsky,Michel"
Date:
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k ob je ct