Re: Proposal: SELECT * EXCLUDE (...) command

From: Hunaid Sohail <hunaidpgml(at)gmail(dot)com>
To: Kacper Kuras <kacperkuras(at)hotmail(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-30 07:06:31
Message-ID: CAMWA6yZPJbS_mU0HXfh7Dzx2gUZT4w2wFd-2YnNVnYZFJOb-Qw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Kacper,

> 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.

Thank you for reviewing the patches.

My colleague, Christoph, pointed out that the patch was missing the
RETURNING part of the documentation. I also noticed that the staroptions
syntax needs to be added to the SELECT INTO documentation page as well.
The documentation needs a few updates, so a new version of the patch is
required.

Meanwhile, we can also wait for further clarification on the standards side.

Regards,
Hunaid Sohail

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-10-30 07:14:38 Re: [PG19] pg_upgrade --check passes, then the upgrade fails
Previous Message Jeevan Chalke 2026-10-30 06:59:41 PL/pgSQL: "missing X at end of SQL expression" is never reported at end of input