Re: [HACKERS] [BUG FIX] Removing NamedLWLockTrancheArray - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: [HACKERS] [BUG FIX] Removing NamedLWLockTrancheArray
Date
Msg-id 20170303.172627.225604431.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] [BUG FIX] Removing NamedLWLockTrancheArray  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: [HACKERS] [BUG FIX] Removing NamedLWLockTrancheArray  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
Sorry for frequent mails..

At Fri, 03 Mar 2017 17:21:21 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote in
<20170303.172121.140674354.horiguchi.kyotaro@lab.ntt.co.jp>
> At Fri, 03 Mar 2017 17:13:42 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote
in<20170303.171342.134582021.horiguchi.kyotaro@lab.ntt.co.jp>
 
> > Hello, some of my collegues found that orafce crashes with
> > postgresql compliled with dtrace.
> > 
> > === The cause
> > 
> > The immediate cause was I think that it just did
> > LWLockNewTrancheId and forget to do LWLockRegisterTranche. But
> > this is hardly detectable by a module developer.
> 
> I'm sorry, I found that orafce is calling LWLockRegisterTranche
> so this might be a different problem but anyway the problem with
> RequestNamedLWLockTranche occurs.

As for orafce, the real cuase seems to be calling
LWLockRagisterTranche with tranche on non-static memory.

regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center





pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] [BUG FIX] Removing NamedLWLockTrancheArray
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] [BUG FIX] Removing NamedLWLockTrancheArray