Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader
Date
Msg-id 20160505203936.GA190373@alvherre.pgsql
Whole thread Raw
In response to Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader  (Andreas Seltenreich <seltenreich@gmx.de>)
List pgsql-hackers
Robert Haas wrote:
> On Thu, May 5, 2016 at 4:11 PM, Andreas Seltenreich <seltenreich@gmx.de> wrote:
> >> Amit Kapila writes:
> >>> Sounds good.  So can we assume that you will try to get us the new report
> >>> with more information?
> >
> > I don't see these crashes anymore in c1543a8.  By the amount of fuzzing
> > done it should have happened a dozen times, so it's highly likely
> > something in 23b09e15..c1543a8 fixed it.
> 
> Hmm, I'd guess c45bf5751b6338488bd79ce777210285531da373 to be the most
> likely candidate.

I thought so too, but then that patch change things in the planner side,
but it seems to me that the reported crash is in the executor, unless I'm
misreading.

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: quickdie doing memory allocations (was atomic pin/unpin causing errors)
Next
From: Andres Freund
Date:
Subject: Re: Is pg_control file crashsafe?