Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIutB-0004Nz-Fq for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2023 17:09:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pIutA-0000Lo-6V for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2023 17:09:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIut9-0000La-TE for pgsql-hackers@lists.postgresql.org; Fri, 20 Jan 2023 17:09:15 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIut7-0004bj-R4 for pgsql-hackers@postgresql.org; Fri, 20 Jan 2023 17:09:15 +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 30KH95j7531252; Fri, 20 Jan 2023 12:09:05 -0500 From: Tom Lane To: Jelte Fennema cc: Magnus Hagander , Alvaro Herrera , Stephen Frost , Noah Misch , Jesse Zhang , Andres Freund , PostgreSQL-development Subject: Re: run pgindent on a regular basis / scripted manner In-reply-to: References: <20200814202651.GA31108@alvherre.pgsql> Comments: In-reply-to Jelte Fennema message dated "Fri, 20 Jan 2023 10:43:50 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <531250.1674234545.1@sss.pgh.pa.us> Date: Fri, 20 Jan 2023 12:09:05 -0500 Message-ID: <531251.1674234545@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jelte Fennema writes: > To me a master branch that pgindent never complains about sounds > amazing! And I personally think rejection of unindented pushes and > cfbot complaining about unindented patches would be a very good thing, > because that seems to be the only solution that could achieve that. The core problem here is that requiring that would translate to requiring every code contributor to have a working copy of pg_bsd_indent. Maybe that's not a huge lift, but it'd be YA obstacle to new contributors, and we don't need any more of those. Yeah, if we switched to some other tool maybe we could reduce the size of that problem. But as Bruce replied, we've not found another one that (a) can be coaxed to make output comparable to what we're accustomed to and (b) seems decently well maintained. regards, tom lane