Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Dmitriy Sarafannikov <dimon99901(at)mail(dot)ru>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc
Date: 2016-01-27 11:23:07
Message-ID: CAFj8pRBMFhMEA9x3PAURcyU68naU0fD9rOdK8708xWzQtDLWAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi

2016-01-27 11:47 GMT+01:00 Dmitriy Sarafannikov <dimon99901(at)mail(dot)ru>:

>
> That's, uh, weird. TopTransactionContext should never be NULL here. This
> is with a stock 9.4.5, without any further extensions configured?
>
>
> It is a stock 9.4.5 with pg_buffercache (1.0) and plv8 (1.4.0) installed
> extensions.
>

I had to fix our log processing extension for 9.5 due NULL
TopTransactionContext. So I can confirm this issue.

When I start database vacuuming by analyze_new_cluster.sh, then Postgres
randomly fails in my extension.

Regards

Pavel

>
> --
> Best regards,
> Dmitriy Sarafannikov
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2016-01-27 11:33:26 Re: BUG #13888: pg_dump write error
Previous Message Dmitriy Sarafannikov 2016-01-27 10:47:18 Re[2]: [BUGS] Segfault in MemoryContextAlloc