Sorry for frequent mails.. At Fri, 03 Mar 2017 17:21:21 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi.kyot...@lab.ntt.co.jp> wrote in <20170303.172121.140674354.horiguchi.kyot...@lab.ntt.co.jp> > At Fri, 03 Mar 2017 17:13:42 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI > <horiguchi.kyot...@lab.ntt.co.jp> wrote in > <20170303.171342.134582021.horiguchi.kyot...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
