Re: Proposal: SELECT * EXCLUDE (...) command - Mailing list pgsql-hackers

From Hunaid Sohail
Subject Re: Proposal: SELECT * EXCLUDE (...) command
Date
Msg-id CAMWA6yYDsUxHzE23Umm48-+Era2LhYNBRv-ber9igY6nZ71SWA@mail.gmail.com
Whole thread
In response to Re: Proposal: SELECT * EXCLUDE (...) command  (Kacper Kuras <kacperkuras@hotmail.com>)
Responses Re: Proposal: SELECT * EXCLUDE (...) command
List pgsql-hackers
Hello,

On Sun, Oct 4, 2026 at 12:54 AM Kacper Kuras <kacperkuras@hotmail.com> wrote:
I think most of this comes from matching names as strings (with
RangeVars from qualified_name_list). BCN-036R1 says the entries in
the exclude list should be resolved the same way as column
references in the select list. So perhaps each entry could be
transformed as an ordinary ColumnRef, and the star expansion could
then skip the columns whose Var matches, without modifying the
namespace item. That would give error positions and correct handling
of aliases and schemas for free.
Thanks for reviewing the patch and reporting bugs. I already switched to
ColumnRef in the upcoming patch since I also found similar kinds of issues.
These issues would hopefully be fixed in the new version.
 
Hunaid, are you planning to post a v3 with the standard syntax? I'd
be glad to test it.
Sorry for the delay, I was busy with some other important stuff during
this period. v3 is around the corner that includes support for new
standard syntax with REPLACE and RENAME clauses.

If everything looks good, you might see a new version of patch this week.
Thanks!

Regards,
Hunaid Sohail

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Ashutosh Sharma
Date:
Subject: Re: Persist slot invalidations before publishing them