Re: [PATCH] pg_bsd_indent: improve formatting of multiline comments

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: [PATCH] pg_bsd_indent: improve formatting of multiline comments
Date: 2026-05-05 13:06:21
Message-ID: CAJ7c6TNVeFYAYFs0KDEVsZNPaZtKtHHq+1Mw7=pTw5Hr3g7KGA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tom,

Thanks for your feedback.

> In this case the problem is that the cleanup pattern only accounts for
> one trailing space. But a variant of this, which I think affects many
> of the steps in the patch, is that there could be tab(s) there. You
> should fix the patterns to allow any number of spaces/tabs at the
> spots where they currently expect just one space. This might result
> in finding cleanups they miss now.

Fair point. Fixed.

> Another amusing diff I noticed:
>
> [...]
>
> Clearly, this is somebody's off-by-one-key typo, and the correct
> fix is s/&/*/. I suspect that fixing that manually is the most
> expedient answer, rather than trying to make pg_bsd_indent smart
> enough to DTRT.

Agree.

> One other nitpick is that the patch itself needs to be run through
> pgperltidy (which has different opinions than your editor about
> tabs vs spaces, apparently).

Fixed in v7.

--
Best regards,
Aleksander Alekseev

Attachment Content-Type Size
v7-0001-pgindent-improve-formatting-of-multiline-comments.patch text/x-patch 2.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Dilip Kumar 2026-05-05 12:55:28 Re: Proposal: Conflict log history table for Logical Replication