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 462D9F98.2030700@sulechow.net
Whole thread Raw
In response to Re: 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
List pgsql-bugs
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
>

Ok, that's the end of the story :) My workmate has confirmed that during
night test PostgreSQL worked perfectly :)

Regards, Marcin

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect
Next
From: Tom Lane
Date:
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298