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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Keith Fiske <keith(at)omniti(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(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:55:58
Message-ID: 20140606205557.GX5146@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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:

> #2 0x000000000079ea87 in ExceptionalCondition (conditionName=conditionName(at)entry=0x9554b0 "!(CritSectionCount == 0 || (CurrentMemoryContext) == ErrorContext || (MyAuxProcType == CheckpointerProcess))", errorType=errorType(at)entry=0x7d94b0 "FailedAssertion", fileName=fileName(at)entry=0x95514e "mcxt.c", lineNumber=lineNumber(at)entry=670) at assert.c:54
> #3 0x00000000007c15e0 in palloc (size=128) at mcxt.c:670
> #4 0x00000000007d8923 in psprintf (fmt=0x975589 "base/%u/%u") at psprintf.c:60
> #5 0x00000000006b4c17 in mdopen (behavior=EXTENSION_FAIL, forknum=MAIN_FORKNUM, reln=0x1107360) at md.c:562

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2014-06-06 20:58:01 Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process
Previous Message Keith Fiske 2014-06-06 20:22:57 Re: BUG #10533: 9.4 beta1 assertion failure in autovacuum process