From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kyle Samson <kysamson(at)tripadvisor(dot)com>, "pgsql-hackers\(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Matthew Kelly <mkelly(at)tripadvisor(dot)com> |
Subject: | Re: Consistent segfault in complex query |
Date: | 2018-09-12 16:08:08 |
Message-ID: | 87h8iupuo7.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> There's a relevant commit from Feb this year (ea6d67cf8)
>> specifically referring to the case of CTEs inside subplans inside
>> EvalPlanQual, which is exactly the scenario you have in your query.
>> So you need to try this in 9.3.22 or later (ideally 9.3.24, the
>> latest) which contain this fix.
Tom> I'm not entirely convinced that that fix will cure this, but
Tom> certainly it seems related, and we should find out whether it has
Tom> any effect.
I agree.
Tom> The reason this seems possibly different is that we're apparently
Tom> returning wrong data out of the sub-select (a zero Datum value,
Tom> but not marked isnull --- if it were, arraycontains wouldn't be
Tom> reached). The previously fixed bug would have caused either
Tom> multiple or missed returns of a valid CTE tuple.
I have some ideas as to why, and I'm poking at them in order to create a
test case (no luck yet, but I'll keep at it).
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2018-09-12 16:13:13 | Re: Consistent segfault in complex query |
Previous Message | Tom Lane | 2018-09-12 16:06:35 | Re: pg_dump test instability |