Re: Alias of VALUES RTE in explain plan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Yasir <yasir(dot)hussain(dot)shah(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Alias of VALUES RTE in explain plan
Date: 2024-11-07 22:27:30
Message-ID: 3509409.1731018450@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just to follow up here --- I put this patch on hold for a few days
because I had to work on release notes. Now I'm glad I did, because
Robert Haas is pushing a proposal that would change the basis of
discussion:

https://www.postgresql.org/message-id/flat/CA%2BTgmoYSYmDA2GvanzPMci084n%2BmVucv0bJ0HPbs6uhmMN6HMg%40mail.gmail.com

If we do what he suggests there, then referencing "*VALUES*" in a
subquery with VALUES and ORDER BY would be broken anyway. In that
case I'd favor committing this patch as-is, to provide users with
a well-defined new behavior. So I think this should stay on hold
a bit longer to see what the outcome of that discussion is.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2024-11-07 22:29:18 Re: [PATCH] pg_stat_activity: make slow/hanging authentication more visible
Previous Message Alexandra Wang 2024-11-07 21:57:58 Re: SQL:2023 JSON simplified accessor support