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

From Keith Parks
Subject RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Date
Msg-id 199912212025.UAA10291@mtcc.demon.co.uk
Whole thread Raw
Responses RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
List pgsql-hackers
"Hiroshi Inoue" <Inoue@tpf.co.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.



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: AW: [HACKERS] LONG varsize - how to go on (pgindent)
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: update_pg_pwd and AR triggers