Re: [PATCH] pg_bsd_indent: improve formatting of multiline comments
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Aleksander Alekseev <aleksander@tigerdata.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Chao Li <li.evan.chao@gmail.com>, Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>, Bruce Momjian <bruce@momjian.us>, Michael Paquier <michael@paquier.xyz>
Date: 2025-12-11T21:48:27Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pgindent: improve formatting of multiline comments.
- 60f9467c3834 19 (unreleased) landed
-
Adjust style of some debugging macros.
- ba1e14134a77 19 (unreleased) landed
-
Fix a couple of comments.
- 123661427b97 19 (unreleased) landed
-
Add IGNORE NULLS/RESPECT NULLS option to Window functions.
- 25a30bbd4235 19 (unreleased) cited
-
Split WaitEventSet functions to separate source file
- 393e0d231405 18.0 cited
With the latest patch applied, I'm still seeing problems with **** and ==== lines in aclcheck.c and analyze.c, as mentioned upthread [0]. I think we should also figure out what we want to do for things like this: ****************************************************************************** - This file contains routines that can be bound to a Postgres backend and - called by the backend in the process of processing queries. The calling - format for these routines is dictated by Postgres architecture. + * This file contains routines that can be bound to a Postgres backend and + * called by the backend in the process of processing queries. The calling + * format for these routines is dictated by Postgres architecture. ******************************************************************************/ Could we modify the patch to leave these kinds of comments alone? [0] https://postgr.es/m/aP-H6kSsGOxaB21k%40nathan -- nathan