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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
Cc: "Keith Parks" <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>, pgman(at)candle(dot)pha(dot)pa(dot)us, wieck(at)debis(dot)com, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Date: 1999-12-17 23:39:21
Message-ID: 11852.945473961@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-12-17 23:41:31 Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Previous Message Jan Wieck 1999-12-17 23:37:19 Re: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock