I should be very tired.
This is the last mail today.
At Fri, 03 Mar 2017 17:26:27 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
<horiguchi.kyot...@lab.ntt.co.jp> wrote in
> > > 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.
No, it is giving static variable. Sorry for the noise.
The problem of postgresql is still exists, though.
NTT Open Source Software Center
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: