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 1qt6Dy-00Aog6-3H for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Oct 2023 13:04:34 +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 1qt6Dv-003x3a-Ek for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Oct 2023 13:04:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qt6Dv-003wzr-2X for pgsql-hackers@lists.postgresql.org; Wed, 18 Oct 2023 13:04:31 +0000 Received: from relay5-d.mail.gandi.net ([2001:4b98:dc4:8::225]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qt6Do-0015df-E3 for pgsql-hackers@postgresql.org; Wed, 18 Oct 2023 13:04:30 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id D16E31C0002; Wed, 18 Oct 2023 13:04:14 +0000 (UTC) Message-ID: <69005b14-a48f-4165-becd-22b14b7a5ec3@postgresfriends.org> Date: Wed, 18 Oct 2023 15:04:13 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: run pgindent on a regular basis / scripted manner To: Tom Lane , Robert Haas Cc: Peter Geoghegan , Andres Freund , Andrew Dunstan , Jelte Fennema , Michael Paquier , "shiy.fnst@fujitsu.com" , Justin Pryzby , Noah Misch , Bruce Momjian , Magnus Hagander , Alvaro Herrera , Stephen Frost , Jesse Zhang , "pgsql-hackers@postgresql.org" , Peter Eisentraut References: <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> <2718058.1697552602@sss.pgh.pa.us> Content-Language: en-US From: Vik Fearing In-Reply-To: <2718058.1697552602@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-GND-Sasl: vik@postgresfriends.org List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/17/23 16:23, Tom Lane wrote: > An alternative I was thinking about after reading your earlier email was > going back to the status quo ante, but doing the manual tree-wide > reindents significantly more often than once a year. Adding one at the > conclusion of each commitfest would be a natural thing to do, for > instance. It's hard to say what frequency would lead to the least > rebasing pain, but we know once-a-year isn't ideal. This is basically how the SQL Committee functions. The Change Proposals (patches) submitted every meeting (commitfest) are always against the documents as they exist after the application of papers (commits) from the previous meeting. One major difference is that Change Proposals are against the text, and patches are against the code. It is not dissimilar to people saying what our documentation should say, and then someone implementing that change. So I am in favor of a pgindent run *at least* at the end of each commitfest, giving a full month for patch authors to rebase before the next fest. -- Vik Fearing