| From: | Hunaid Sohail <hunaidpgml(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal: SELECT * EXCLUDE (...) command |
| Date: | 2026-02-16 08:20:58 |
| Message-ID: | CAMWA6yYu5qMyHHd-oDG6jKz1NahUuE7=9EraNDqnntZ_xEnhqQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
PFA v2 of the patch fixing behavior described in
examples 2, 3, 5, 8, and 11 from the proposal paper.
I have also expanded the test cases to cover the
relevant behaviors described in the paper.
The ambiguous column behavior described in example 6
is not changed in this patch, but it can be easily updated
with a simple if condition if required.
Regards,
Hunaid Sohail
>
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Implement-SELECT-EXCLUDE-.-command.patch | application/x-patch | 39.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2026-02-16 08:27:56 | Re: Flush some statistics within running transactions |
| Previous Message | Andy Pogrebnoi | 2026-02-16 08:19:21 | Re: Lowering the default wal_blocksize to 4K |