From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [BUG FIX] Removing NamedLWLockTrancheArray |
Date: | 2017-03-03 08:31:19 |
Message-ID: | 20170303.173119.145303756.horiguchi.kyotaro@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <20170303(dot)172627(dot)225604431(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.
No, it is giving static variable. Sorry for the noise.
The problem of postgresql is still exists, though.
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-03-03 09:28:54 | Re: patch: function xmltable |
Previous Message | Kyotaro HORIGUCHI | 2017-03-03 08:26:27 | Re: [BUG FIX] Removing NamedLWLockTrancheArray |