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 1qsmkt-009NYY-Ms for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Oct 2023 16:17:15 +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 1qsmkr-00Boks-3Q for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Oct 2023 16:17:13 +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 1qsmkq-00Bokk-QA for pgsql-hackers@lists.postgresql.org; Tue, 17 Oct 2023 16:17:13 +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 1qsmkn-001Ci3-IU for pgsql-hackers@postgresql.org; Tue, 17 Oct 2023 16:17:12 +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 39HGGtsh2817121; Tue, 17 Oct 2023 12:16:55 -0400 From: Tom Lane To: Peter Geoghegan cc: Jelte Fennema , Robert Haas , Andres Freund , Andrew Dunstan , 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 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> <2718058.1697552602@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Tue, 17 Oct 2023 09:07:05 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2817119.1697559415.1@sss.pgh.pa.us> Date: Tue, 17 Oct 2023 12:16:55 -0400 Message-ID: <2817120.1697559415@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > That's beside the point. The point is that I'm obligated to keep > typedef.list up to date in general, a task that is made significantly > harder by random objdump implementation details. And I probably need > to do this not just once per commit, but several times, since in > practice I need to defensively run and rerun pgindent as the patch is > tweaked. Hmm, I've not found it that hard to manage the typedefs list. If I run pgindent and it adds weird spacing around uses of a new typedef name, I go "oh, I better add that to the list" and do so. End of problem. There's not a requirement that you remove disused typedef names, nor that you alphabetize perfectly. I'm content to update those sorts of details from the buildfarm's list once a year or so. This does assume that you inspect pgindent's changes rather than just accepting them blindly --- but as I commented upthread, the tool really requires that anyway. regards, tom lane