| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Provide support for trailing commas |
| Date: | 2026-01-08 05:51:14 |
| Message-ID: | 86BF995D-5959-458C-8F63-DDDB250B058B@anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On January 7, 2026 11:44:29 PM EST, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>On Tue, Jan 6, 2026 at 03:35:38PM -0500, Greg Sabino Mullane wrote:
>> tl;dr Provide support for trailing commas, where possible and practical.
>>
>> (Disclaimer: No LLM or AI was used to craft this patch or this email)
>>
>> Happy New Year! Please find attached a patch to provide comprehensive trailing
>> comma support, where we allow (when possible) a comma that does NOT come before
>> the next item in a list. To wit:
>
>I am unclear why you bothered to create and work on such a large email
>and patch rather than ask if this was a desired change; see:
>
> https://wiki.postgresql.org/wiki/Todo#Development_Process
Meh. This kind of change really needs information about the implementation cost to be judged. The process described there rarely is a good idea for anybody that has some community experience.
Greetings,
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2026-01-08 05:55:46 | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |
| Previous Message | Amit Kapila | 2026-01-08 05:26:18 | Re: Simplify code building the LR conflict messages |