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

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

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date: 2007-04-24 12:26:02
Message-ID: 20070424122602.GA15856@svr2.hagander.net (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Tue, Apr 24, 2007 at 02:25:41AM -0400, 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.

Well, better safe than sorry :-)

Committed now. Thanks for testing, even though Tom claims it's unnecessary
:-P

//Magnus

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2007-04-24 12:50:17
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect
Previous:From: Heikki LinnakangasDate: 2007-04-24 11:51:34
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2007-04-24 12:50:17
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect
Previous:From: Heikki LinnakangasDate: 2007-04-24 11:51:34
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