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

From Tom Lane
Subject Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Date
Msg-id 11852.945473961@sss.pgh.pa.us
Whole thread Raw
In response to RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
List pgsql-hackers
"Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> It seems that conflicts of the initialization of some backends cause
> above NOTICE messages.
> Those backends would use the same XIDTAGs for the same relations
> in case of LockAcquire()/LockRelease() because xids of those backends
> are'nt set before starting the first command. When one of the backend
> call LockReleaseAll(),it would release all together.

Oooh, that would nicely explain Keith's observation that it seems to
happen at backend startup.  I guess we need to select an initial XID
earlier during startup than we now do?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Anyone for prettyprinted EXPLAIN VERBOSE?
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock