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.94.2) (envelope-from ) id 1qsYDA-008R62-5P for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Oct 2023 00:45:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qsYD7-005Mma-HT for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Oct 2023 00:45:26 +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.94.2) (envelope-from ) id 1qsYD7-005MmS-8C for pgsql-hackers@lists.postgresql.org; Tue, 17 Oct 2023 00:45:25 +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.94.2) (envelope-from ) id 1qsYD2-0015XE-Q9 for pgsql-hackers@postgresql.org; Tue, 17 Oct 2023 00:45:25 +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 39H0j0wo2620573; Mon, 16 Oct 2023 20:45:00 -0400 From: Tom Lane To: Peter Geoghegan cc: Andres Freund , Andrew Dunstan , Jelte Fennema , Michael Paquier , "shiy.fnst@fujitsu.com" , Robert Haas , Justin Pryzby , Noah Misch , Bruce Momjian , Magnus Hagander , Alvaro Herrera , Stephen Frost , Jesse Zhang , "pgsql-hackers@postgresql.org" , Peter Eisentraut Subject: Re: run pgindent on a regular basis / scripted manner In-reply-to: References: <30a72ba4-9ca4-15b5-db0f-0e68cba7ab26@dunslane.net> <1f594a4b-14c8-e159-b250-edf8a091320d@dunslane.net> <20230811212511.aih23qfthi24zhq4@awork3.anarazel.de> <338202.1691793002@sss.pgh.pa.us> <342032.1691794926@sss.pgh.pa.us> <8c4d8afb-cda1-299c-8011-f60cdaff3999@dunslane.net> <20230812211404.sydbwo2juu7vyhtg@awork3.anarazel.de> <530189.1691880417@sss.pgh.pa.us> <544112.1691886017@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Sun, 15 Oct 2023 17:52:17 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2620571.1697503500.1@sss.pgh.pa.us> Date: Mon, 16 Oct 2023 20:45:00 -0400 Message-ID: <2620572.1697503500@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > There were two independent fixup commits to address complaints from > koel just today (from two different committers). Plus there was a > third issue (involving a third committer) this past Wednesday. > This policy isn't working. Two thoughts about that: 1. We should not commit indent fixups on behalf of somebody else's misindented commit. Peer pressure on committers who aren't being careful about this is the only way to improve matters; so complain to the person at fault until they fix it. 2. We could raise awareness of this issue by adding indent verification to CI testing. I hesitate to suggest that, though, for a couple of reasons: 2a. It seems fairly expensive, though I might be misjudging. 2b. It's often pretty handy to submit patches that aren't fully indent-clean; I have such a patch in flight right now at [1]. 2b could be ameliorated by making the indent check be a separate test process that doesn't obscure the results of other testing. regards, tom lane [1] https://www.postgresql.org/message-id/2617358.1697501956%40sss.pgh.pa.us