From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [sqlsmith] Failing assertions in spgtextproc.c |
Date: | 2015-12-18 23:07:48 |
Message-ID: | CAM3SWZTvJC0Jh3mGYO5jceR_+KRZq5wNif0AdKupfs+x=e4JOQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 18, 2015 at 1:23 PM, Andreas Seltenreich <seltenreich(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2015-12-19 00:50:50 | Re: pg_tables bug? |
Previous Message | Gaetano Mendola | 2015-12-18 22:55:26 | Re: pg_tables bug? |