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

From: Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>
To: Inoue(at)tpf(dot)co(dot)jp
Cc: hackers(at)postgresql(dot)org
Subject: RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Date: 1999-12-21 20:25:05
Message-ID: 199912212025.UAA10291@mtcc.demon.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
>> >I'm not sure it's possible or not.
>> >If startup sequence in InitPostgres() is changed,we may hardly
>> >find the place to start transaction during backend startup.
>> >
>> >Seems the unique place we could call StartTransacationCommand()
>> >during backend startup is between InitCatalogCahe() and InitUserId()
>> >in InitPostgres() now.
>> >I tried the following patch and it seems work at least now.
>>
>> <snip>
>> Hiroshi
>>
>> I concur, after application of this patch I've not had a single
>> lock NOTICE: error in the regression tests.
>>
>
>Thanks.
>
>I'm not sure my patch has no problem.
>May I dare to commit it to current tree ?
>

I've not seen any problems so-far.

Can you commit your patch for wider testing?

Keith.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-12-21 22:31:40 update_pg_pwd and AR triggers
Previous Message Bruce Momjian 1999-12-21 17:36:10 Re: AW: [HACKERS] LONG varsize - how to go on (pgindent)