Skip site navigation (1) Skip section navigation (2)

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

From: Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)net>
To: magnus(at)hagander(dot)net
Cc: pgsql-bugs(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date: 2007-04-24 06:11:36
Message-ID: 462D9F98.2030700@sulechow.net (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
> 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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-04-24 06:25:41
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Previous:From: Tom LaneDate: 2007-04-24 06:10:12
Subject: Re: RETURN QUERY in PL/PgSQL?

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-04-24 06:25:41
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Previous:From: Tom LaneDate: 2007-04-24 04:37:20
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group