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 1pK38C-0008IJ-EW for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Jan 2023 20:09:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pK38A-0000JT-DI for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Jan 2023 20:09:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pK38A-0000JK-3q for pgsql-hackers@lists.postgresql.org; Mon, 23 Jan 2023 20:09:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pK383-0005dN-G2 for pgsql-hackers@postgresql.org; Mon, 23 Jan 2023 20:09:24 +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 30NK9AUQ1921831; Mon, 23 Jan 2023 15:09:10 -0500 From: Tom Lane To: Nikita Malakhov cc: Alvaro Herrera , Andres Freund , Jelte Fennema , Peter Geoghegan , Bruce Momjian , Magnus Hagander , Stephen Frost , Noah Misch , Jesse Zhang , PostgreSQL-development Subject: Re: run pgindent on a regular basis / scripted manner In-reply-to: References: <20230123162225.5ynn7qgjdshpqiyn@alvherre.pgsql> <20230123173820.5taw5j5axceifsdz@alvherre.pgsql> Comments: In-reply-to Nikita Malakhov message dated "Mon, 23 Jan 2023 21:54:15 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1921829.1674504550.1@sss.pgh.pa.us> Date: Mon, 23 Jan 2023 15:09:10 -0500 Message-ID: <1921830.1674504550@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nikita Malakhov writes: > I've ran pdindent on the whole Postgres and it'd changed > an awful lot of source files. Won't it create a lot of merge conflicts? Well, yeah, you've rediscovered the fact that a lot of commits are sloppy about this, and it's been awhile since our last tree-wide pgindent. Our normal process has been to do a cleanup pgindent run annually or so, usually after the end of the last commitfest of a cycle when there's plenty of time for people to deal with the ensuing merge conflicts. If we could get to "commits are pgindent clean to begin with", we could avoid the merge problems from one-big-reindent. I'd still be inclined to do an annual run as a backup, but hopefully it would find few problems. regards, tom lane