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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Dmitriy Sarafannikov <dimon99901(at)mail(dot)ru>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc
Date: 2016-01-27 12:26:22
Message-ID: 8F98BBF2-97FA-42D5-BD47-2EA050657773@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On January 27, 2016 12:23:07 PM GMT+01:00, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>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.

But this report isn't about 9.5 afaics.

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

What exactly does your extension do? And where did you add that null check?

Andres

---
Please excuse brevity and formatting - I am writing this on my mobile phone.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2016-01-27 12:36:21 Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc
Previous Message Alvaro Herrera 2016-01-27 11:33:26 Re: BUG #13888: pg_dump write error