Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vU5pP-00Gq8J-1w for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Dec 2025 16:17:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vU5pN-008ea4-2P for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Dec 2025 16:17:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vU5pN-008eZv-1S for pgsql-hackers@lists.postgresql.org; Fri, 12 Dec 2025 16:17:10 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vU5pL-000NRW-2V for pgsql-hackers@lists.postgresql.org; Fri, 12 Dec 2025 16:17:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 5BCGH1wD1000975; Fri, 12 Dec 2025 11:17:01 -0500 From: Tom Lane To: =?utf-8?Q?=C3=81lvaro?= Herrera cc: Aleksander Alekseev , PostgreSQL Hackers , Nathan Bossart , Chao Li , Arseniy Mukhin , Bruce Momjian , Michael Paquier Subject: Re: [PATCH] pg_bsd_indent: improve formatting of multiline comments In-reply-to: <202512121547.dwkzxcs56227@alvherre.pgsql> References: <202512121547.dwkzxcs56227@alvherre.pgsql> Comments: In-reply-to =?utf-8?Q?=C3=81lvaro?= Herrera message dated "Fri, 12 Dec 2025 16:53:39 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1000973.1765556221.1@sss.pgh.pa.us> Date: Fri, 12 Dec 2025 11:17:01 -0500 Message-ID: <1000974.1765556221@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =?utf-8?Q?=C3=81lvaro?= Herrera writes: > It's strange to see this thread go on about messing with the Perl script > because we're too afraid of pg_bsd_indent. Maybe we should take > ownership of that code -- improve its own indentation to our > conventions, add comments, rename unclear variables, and so on until we > have something we can work with, and fix these weird bugs and > idiosincratic behaviors we don't like. I just found out this code dates > back from 1976. I've worked with that code a little bit, and it's mostly unreadable spaghetti :-(. If somebody wants to make an effort to make it not so awful, that'd be great, but I fear it's a very nontrivial project. Having said that, we've already basically forked it from the NetBSD upstream, so there is no reason not to diverge further. > We have a _huge_ regression test for it: our own source code repository. > It's not like any breakage is going to go unnoticed. True. regards, tom lane