Re: Consistent segfault in complex query

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Kyle Samson <kysamson(at)tripadvisor(dot)com>
Cc: "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:21:57
Message-ID: 878t46pu1b.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Andrew" == Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
>>>>> "Kyle" == Kyle Samson <kysamson(at)tripadvisor(dot)com> writes:

Kyle> This is on a 9.3.19 server and we saw no
Kyle> mention of a fix in the release notes since this version and we
Kyle> do not know if it affects later major releases as well.

Andrew> There's a relevant commit from Feb this year (ea6d67cf8)
Andrew> specifically referring to the case of CTEs inside subplans
Andrew> inside EvalPlanQual, which is exactly the scenario you have in
Andrew> your query. So you need to try this in 9.3.22 or later (ideally
Andrew> 9.3.24, the latest) which contain this fix.

Kyle, you can disregard this suggestion because I've now confirmed the
bug still exists in 9.3.24 (actually in REL9_3_STABLE head).

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2018-09-12 16:33:22 Re: Consistent segfault in complex query
Previous Message Tom Lane 2018-09-12 16:14:00 Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT