Re: [BUG FIX] Removing NamedLWLockTrancheArray

Sorry for frequent mails..

At Fri, 03 Mar 2017 17:21:21 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <20170303(dot)172121(dot)140674354(dot)horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
> At Fri, 03 Mar 2017 17:13:42 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <20170303(dot)171342(dot)134582021(dot)horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)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