From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: magical eref alias names |
Date: | 2024-11-07 21:32:29 |
Message-ID: | 3488508.1731015149@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
BTW, one aspect of this proposal that needs to be discussed is that
it can break existing SQL. An example discussed nearby[1] is
regression=# select * from (values (1,7), (3,4) order by "*VALUES*".column2);
column1 | column2
---------+---------
3 | 4
1 | 7
(2 rows)
We concluded in the other thread that we didn't want to risk breaking
such code. I concede that this example isn't too compelling on its
own, but I wonder if there's other cases that are more likely to be
in common use.
(If we do decide it's okay to break this, my opinion about what to
do in the other thread would change.)
regards, tom lane
[1] https://www.postgresql.org/message-id/251197.1730222362%40sss.pgh.pa.us
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2024-11-07 21:34:54 | Re: index prefetching |
Previous Message | Devulapalli, Raghuveer | 2024-11-07 21:30:32 | RE: Use __attribute__((target(sse4.2))) for SSE42 CRC32C |