Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock

wieck(at)debis(dot)com (Jan Wieck)
>Bruce Momjian wrote:
>
>> > Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)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.
>
>
> Also, I used it after another dozen times without. Now I see
> them too. So I assume it was a recent change that introduced
> the problem.

I'm not sure it's that recent, I think I've had 1 or 2 such errors
ever since I've been running the "runcheck".

What I will say is that the parallel running arrived at around the
same time as the new psql and I didn't have an old version available
to run the tests until sometime after. (had to download and build 6.5!)

>
> And if not, much better. Would show that running all tests
> serialized had hidden a bug for a long time.
>

Quite possible, although something recent has aggrevated it somewhat ;-)

Keith.