Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Keith Fiske <keith(at)omniti(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, levertond(at)googlemail(dot)com, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process
Date: 2014-06-06 20:58:01
Message-ID: 20140606205801.GB23201@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2014-06-06 16:55:58 -0400, Alvaro Herrera wrote:
> Keith Fiske wrote:
> > Not sure if this is the same issue originally reported, but the description
> > sounded the same. I can get this to happen pretty reliably in 9.4beta1 with
> > the pgtap test suite for one of my extensions -
>
> Uh, this is a completely different problem. We discussed long ago that
> those pallocs in relpath() were going to cause a problem:

I actually don't think it's a different problem. If we'd restructure
things so the critical sections are separate this wouldn't be a
problem. It's imo not a particularly good idea to mdopen() inside a
critical section either.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Keith Fiske 2014-06-06 21:44:18 Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process
Previous Message Alvaro Herrera 2014-06-06 20:55:58 Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process