Re: [sqlsmith] Failing assertions in spgtextproc.c - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [sqlsmith] Failing assertions in spgtextproc.c
Date
Msg-id CAM3SWZTvJC0Jh3mGYO5jceR_+KRZq5wNif0AdKupfs+x=e4JOQ@mail.gmail.com
Whole thread Raw
In response to [sqlsmith] Failing assertions in spgtextproc.c  (Andreas Seltenreich <seltenreich@gmx.de>)
Responses Re: [sqlsmith] Failing assertions in spgtextproc.c  (Andreas Seltenreich <seltenreich@gmx.de>)
List pgsql-hackers
On Fri, Dec 18, 2015 at 1:23 PM, Andreas Seltenreich <seltenreich@gmx.de> wrote:
> I do see two assertions in spgtextproc.c fail on occasion when testing
> with sqlsmith:
>
> TRAP: FailedAssertion([...], File: "spgtextproc.c", Line: 424)
> TRAP: FailedAssertion([...], File: "spgtextproc.c", Line: 564)
>
> I can't reproduce it reliably but looking at the coredumps, the failing
> part of the expression is always
>
>     in->level == 0 && DatumGetPointer(in->reconstructedValue) == NULL
>
> In all of the dumps I looked at, in->reconstructedValue contains a
> zero-length text instead of the asserted NULL, and the tuples fed to
> leaf_consistent()/inner_consistent() look like the one below.

Can you do this?:

(gdb) p debug_query_string

It's a global variable, often useful in these situations.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Gaetano Mendola
Date:
Subject: Re: pg_tables bug?
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_tables bug?