Re: Alias of VALUES RTE in explain plan - Mailing list pgsql-hackers

From Yasir
Subject Re: Alias of VALUES RTE in explain plan
Date
Msg-id CAA9OW9dLo34sT7xE1fA_fncs-J2e+qAC3dkCKs=zynmLQVt3qg@mail.gmail.com
Whole thread Raw
In response to Re: Alias of VALUES RTE in explain plan  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Alias of VALUES RTE in explain plan
List pgsql-hackers


On Mon, Oct 28, 2024 at 1:07 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Yasir <yasir.hussain.shah@gmail.com> writes:
> On Sat, Oct 26, 2024 at 12:21 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I forgot to mention a third problem, which is that reassigning the
>> alias during subquery pullup means it doesn't happen if subquery
>> pullup doesn't happen.

> Yes, that is by design.

By design?  How can you claim that's not a bug?  The alias(es)
associated with a VALUES clause surely should not vary depending
on whether the clause includes a volatile function --- not to
mention other unobvious reasons for flattening to happen or not.

By design of my solution, I was not taking it as a bug. But now, I agree with your opinion. 
 

                        regards, tom lane

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: libedit history seems to be misbehaving / broken
Next
From: Noah Misch
Date:
Subject: Re: race condition in pg_class