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

Re: How to handle waitingForLock in LockWaitCancel()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: How to handle waitingForLock in LockWaitCancel()
Date: 2001-03-06 02:25:17
Message-ID: 3607.983845517@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
>> I suspect you will find that these crashes occur during the window just
>> after

> Sorry what does 'just after' mean ?
> Isn't it during the semop() ?

>> the semop() call in IpcSemaphoreLock() --- see the comment

If an interrupt during the semop led to a crash, it would be easy to
reproduce.  I suspect that the crash condition arises only when the
interrupt occurs in a narrow time window ... such as the few
instructions just before or just after the semop call.  It's just a
hunch though.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-03-06 02:28:20
Subject: Re: How to shoot yourself in the foot: kill -9 postmaster
Previous:From: Lamar OwenDate: 2001-03-06 02:23:55
Subject: Re: How to shoot yourself in the foot: kill -9 postmaster

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