Re: Soon-to-be-broken regression test case
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
Jeevan Chalke <jeevan.chalke@enterprisedb.com>,
pgsql-hackers@lists.postgresql.org,
David Rowley <david.rowley@2ndquadrant.com>
Date: 2018-10-11T16:45:24Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > On 2018-Oct-11, Tom Lane wrote: >> I have been fooling around with a patch to allow pull-up of sub-selects >> that lack any FROM, along the lines discussed in >> https://www.postgresql.org/message-id/15944.1521127664@sss.pgh.pa.us >> I find that it is smart enough to reduce that EXISTS to a plain >> expression, yielding >> >> QUERY PLAN >> ---------------------------------------------------- >> Subquery Scan on tenk1_vw_sec >> -> Index Only Scan using tenk1_unique1 on tenk1 >> Index Cond: (unique1 = 0) >> (3 rows) > Hmm, I have the feeling that this would nullify some tests in > partition_prune also, which IIRC pretend to invoke runtime pruning with > things like "WHERE partcol = (select 1)". Hm, I'm not seeing any regression test result changes there. However, if you're just executing queries and not EXPLAIN'ing them, it's possible something unwanted is happening under the hood. regards, tom lane
Commits
-
Make some subquery-using test cases a bit more robust.
- b403ea43e40a 12.0 landed
-
Prevent generation of bogus subquery scan paths.
- dc1057fcd878 11.0 cited