Re: Soon-to-be-broken regression test case - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Soon-to-be-broken regression test case
Date
Msg-id 5749.1539276324@sss.pgh.pa.us
Whole thread Raw
In response to Re: Soon-to-be-broken regression test case  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Soon-to-be-broken regression test case  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Soon-to-be-broken regression test case
Next
From: Alvaro Herrera
Date:
Subject: Re: Soon-to-be-broken regression test case