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

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Dmitriy Sarafannikov <dimon99901(at)mail(dot)ru>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc
Date: 2016-01-27 12:36:21
Message-ID: CAFj8pRBiU5ErMWM-SzSC1gRY3jZ=0z9jcdOv2Jk-Wge6z+3X5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2016-01-27 13:26 GMT+01:00 Andres Freund <andres(at)anarazel(dot)de>:

> 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?
>

this extension does some log preprocessing for syslog

extension and fix attached

Regards

Pavel

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

Attachment Content-Type Size
gdlogger.patch text/x-patch 6.0 KB
gdlogger-9.5-fix.patch text/x-patch 2.1 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message otheus uibk 2016-01-27 13:03:37 << unrecognized configuration parameter "pg_stat_statements.track" >>
Previous Message Andres Freund 2016-01-27 12:26:22 Re: Re[2]: [BUGS] Segfault in MemoryContextAlloc