Re: BUG #1512: Assertion failure (lock.c:1537) with SELECT FOR UPDATE and savepoints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stephen Clouse" <stephenc(at)theiqgroup(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1512: Assertion failure (lock.c:1537) with SELECT FOR UPDATE and savepoints
Date: 2005-03-01 21:20:57
Message-ID: 22543.1109712057@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> ISTM we have to fix RemoveFromWaitQueue to remove the proclock object
> immediately if its count has gone to zero. It should be impossible
> for the lock's count to have gone to zero (that would imply no one
> else holds the lock, so we couldn't be waiting on it) so an Assert
> is sufficient for that part.

I've applied a patch along these lines; it seems to make the problem
go away.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris Hutchinson 2005-03-02 03:59:52 BUG #1513: pg_dump -t doesn't include sequences for pre-v8-created tables
Previous Message Magnus Hagander 2005-03-01 19:40:50 Re: bcmwltry.exe, libeay32.dll