| From: | Kacper Kuras <kacperkuras(at)hotmail(dot)com> |
|---|---|
| To: | Hunaid Sohail <hunaidpgml(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Christoph Berg <myon(at)debian(dot)org>, Robert Treat <rob(at)xzilla(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: SELECT * EXCLUDE (...) command |
| Date: | 2026-10-29 18:19:25 |
| Message-ID: | VI0P193MB3111EB6F4AF8CDF354F91C91BF6E2@VI0P193MB3111.EURP193.PROD.OUTLOOK.COM |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Hunaid,
Thanks for v4. I applied it to current master and went through the
cases from my earlier mails again. Everything I raised on v3 is
addressed, the minor points too. In particular, star options are
rejected outside the select list, RETURNING works (including OLD/NEW,
REPLACE and RENAME), new.* (EXCLUDE (old.x)) is rejected, and a bad
qualifier now gets the same error as in a select list. cfbot is green
as well.
One cosmetic point, take it or leave it: applyStarOptions() goes
through the lists in five quite similar loops. A small helper that
returns the matching item from one list and reports duplicates would
cut it down to finding the three items, checking the EXCLUDE
conflicts, and applying REPLACE and RENAME.
From my side the patch looks ready, so I'm marking it Ready for
Committer. The main open question is whether the behavior matches
what was accepted into the standard, e.g. for ambiguous names, and
that needs Peter's input.
Regards,
Kacper Kuras
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Burd, Greg | 2026-10-29 18:11:29 | Re: Return pg_control from pg_backup_stop(). |