At Mon, 6 Mar 2017 19:32:25 +0530, Amit Kapila wrote
in
> In RegisterLWLockTranches(), we do register the named tranches as well
> which should make it available in LWLockTrancheArray. Do you see any
> reason why that shouldn't work?
Ouch! I mingled the two cases
together. RequestNamedLWLockTr
On Mon, Mar 6, 2017 at 1:37 PM, Kyotaro HORIGUCHI
wrote:
> Ok, I think I understand the complete picture.
>
> At Mon, 06 Mar 2017 15:58:56 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
> wrote in
> <20170306.155856.198084190.horiguchi.kyot...@lab.ntt.co.jp>
>> > I can guess two ways to fix thi
By the way,
At Mon, 06 Mar 2017 17:07:55 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20170306.170755.68410634.horiguchi.kyot...@lab.ntt.co.jp>
> Ok, I think I understand the complete picture.
>
> At Mon, 06 Mar 2017 15:58:56 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
> wrote
Ok, I think I understand the complete picture.
At Mon, 06 Mar 2017 15:58:56 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20170306.155856.198084190.horiguchi.kyot...@lab.ntt.co.jp>
> > I can guess two ways to fix this. One is change the definition of
> > T_NAME.
> >
> > | #define T_
At Mon, 06 Mar 2017 15:44:52 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20170306.154452.254472341.horiguchi.kyot...@lab.ntt.co.jp>
> Hello,
>
> At Sat, 4 Mar 2017 10:07:50 +0530, Amit Kapila
> wrote in
> > On Fri, Mar 3, 2017 at 3:49 PM, Kyotaro HORIGUCHI
> > wrote:
> > >> You
Hello,
At Sat, 4 Mar 2017 10:07:50 +0530, Amit Kapila wrote
in
> On Fri, Mar 3, 2017 at 3:49 PM, Kyotaro HORIGUCHI
> wrote:
> >> You can read about usage of LWLocks in extensions from below location:
> >> https://www.postgresql.org/docs/devel/static/xfunc-c.html#idp86986416
> >
> > Thank you f
On Fri, Mar 3, 2017 at 3:49 PM, Kyotaro HORIGUCHI
wrote:
>> You can read about usage of LWLocks in extensions from below location:
>> https://www.postgresql.org/docs/devel/static/xfunc-c.html#idp86986416
>
> Thank you for the pointer. I understand that the document describes the only
> correct way
> You can read about usage of LWLocks in extensions from below location:
> https://www.postgresql.org/docs/devel/static/xfunc-c.html#idp86986416
Thank you for the pointer. I understand that the document describes the
only correct way to use LWLock in extensions and using
LWLockRegisterTranche is
On Fri, Mar 3, 2017 at 1:43 PM, Kyotaro HORIGUCHI
wrote:
> 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 i
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
wrote in
<20170303.172627.225604431.horiguchi.kyot...@lab.ntt.co.jp>
> > > Hello, some of my collegues found that orafce crashes with
> > > postgresql compliled with
Sorry for frequent mails..
At Fri, 03 Mar 2017 17:21:21 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
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
> wrote in
> <20170303.171342.134582021.ho
At Fri, 03 Mar 2017 17:13:42 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
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 thin
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.
Typical tracepoint looks li
13 matches
Mail list logo