Обсуждение: RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock

"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.

> -----Original Message-----
> From: Keith Parks [mailto:emkxp01@mtcc.demon.co.uk]
> 
> "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?
>

OK,I have commited the patch to current tree now.
I had no time to do it yesterday,sorry.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp