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

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

From: "Marcin Waldowski" <M(dot)Waldowski(at)sulechow(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date: 2007-04-19 09:43:03
Message-ID: 200704190943.l3J9h38o003664@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
The following bug has been logged online:

Bug reference:      3242
Logged by:          Marcin Waldowski
Email address:      M(dot)Waldowski(at)sulechow(dot)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: 

Hello.

After some time of performace test of our aplication (50 concurrent database
connections making lots of quick transactions with prepared statements) we
found problem in PostgreSQL log - "could not unlock semaphore: error code
298". After that connections were hanged blocked on update operations.

We are investigating problem now. What another information should we
provide?

Log from 8.2.1
2007-04-19 08:52:11 FATAL:  could not unlock semaphore: error code 298
2007-04-19 08:52:11 STATEMENT:  COMMIT
2007-04-19 08:52:11 WARNING:  AbortTransaction while in COMMIT state

Log from 8.2.3
2007-04-19 10:56:13 FATAL:  could not unlock semaphore: error code 298
2007-04-19 10:56:13 STATEMENT:  update sometable set a = a + $1, b = b + $2,
c = c + $3 where id = $4

Regards, Marcin

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2007-04-19 11:02:19
Subject: Re: Load distributed checkpoint V4
Previous:From: Zoltan BoszormenyiDate: 2007-04-19 09:19:40
Subject: parser dilemma

pgsql-bugs by date

Next:From: Marcin WaldowskiDate: 2007-04-19 12:50:19
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Previous:From: Magnus HaganderDate: 2007-04-19 07:21:05
Subject: Re: BUG #3232: Regression: pgsql server startup problem with encrypted partitions

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