Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Date
Msg-id 199912160346.WAA17074@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
List pgsql-hackers
> Keith Parks <emkxp01@mtcc.demon.co.uk> writes:
> > Since the new parallel regression tests I've always had a few
> > lock NOTICE messages like the following.
> 
> Interesting --- I had not run the parallel test for a while,
> but I tried it just now and got half a dozen of these:
>     NOTICE:  LockRelease: locktable lookup failed, no lock
> (Otherwise the tests all passed.)
> 
> Something's been broken fairly recently.  Does anyone have an
> idea what changed?

Good question.  I can't imagine what it would be.  We didn't do much,
and parallel regression is not that old.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] "ExecInitIndexScan: both left and right..." meaning?