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 1pOA0v-0005YH-RF for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Feb 2023 04:18:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pOA0t-0005G2-4i for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Feb 2023 04:18:55 +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 1pOA0s-0005Ft-R6 for pgsql-hackers@lists.postgresql.org; Sat, 04 Feb 2023 04:18:54 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pOA0q-00029Z-F9 for pgsql-hackers@postgresql.org; Sat, 04 Feb 2023 04:18:53 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-16332831ed0so8982954fac.10 for ; Fri, 03 Feb 2023 20:18:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=bH8L7o4zpOQuRt7/159pU0v3/9U2BnpXwSlA+7QNTPE=; b=d20UE7NDzrfN5SmzR3U2jrkhhIEtIANGxKiBMgra7AROzuKt5YOLgcck3BayXMb+8e N//g+/t0py4tbdcVB79nQtSbs+HtZWDg1z08FCg4IW7L2TaSw7vPpFVZdp4H23bm9BhZ mPjUzqtYXhiHafsn8toOB2/ggD74gHwRTiFKA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=bH8L7o4zpOQuRt7/159pU0v3/9U2BnpXwSlA+7QNTPE=; b=qYVZ9LB0AhDNZedQp31xd3+4WzkUvjVlKMq+Z2W5maKjVtQi3bVm+0RbwI9x9u4rm2 f3vMvdQmL8E2siRHYG2r+l6++sXZj6tpqyC7FqPbrhRfNNEcSKmtSa2Mey0YQQwQreGc F+pocQJzJFPJAvJB0pQnamytnE7GjB5rFLr8YGe82tTl1ws/O0FYwfuIBvtbhYTPE8ds LmkMKjTCIUGBfa5pB4wO02DW1jXWwjl/tMAYEd4nJon8vTPolDpZvZ617mxpJhCjYXtC nQylkQ2KopLrnt85fz0WhyG+AyfBsrxpRVXm0y6uaSBsxAwyvmlenpf1CmXLmgcFWO0j /lFg== X-Gm-Message-State: AO0yUKXXQa4zbOn4mCH66Zs5IuAJoZmjz1KyunMCevp6SXb02p1zDCEN OQYY1/qUyqOQRBwJ3cHemdJRyg== X-Google-Smtp-Source: AK7set9AQmlg5Pk0y0vz2OjnK9yWy+KE5G9NnnTT2Q+yUfh8wU3RHvXrUzDje0TRMLRZbZIMimd3xw== X-Received: by 2002:a05:6870:73c9:b0:163:319f:d2c with SMTP id a9-20020a05687073c900b00163319f0d2cmr6804612oan.57.1675484331845; Fri, 03 Feb 2023 20:18:51 -0800 (PST) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id a28-20020a4a9b1c000000b004f227a05684sm1720625ook.34.2023.02.03.20.18.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Feb 2023 20:18:51 -0800 (PST) Date: Fri, 3 Feb 2023 20:18:48 -0800 From: Noah Misch To: Tom Lane Cc: Andrew Dunstan , Andres Freund , Jelte Fennema , Peter Geoghegan , Bruce Momjian , Magnus Hagander , Alvaro Herrera , Stephen Frost , Jesse Zhang , PostgreSQL-development Subject: Re: run pgindent on a regular basis / scripted manner Message-ID: <20230204041848.GC1896331@rfd.leadboat.com> References: <1097305.1674334785@sss.pgh.pa.us> <20230121224312.qmwpagrebidr6hi7@awork3.anarazel.de> <20230122094957.x542ojaqgi4lalq4@awork3.anarazel.de> <20230122223806.3sgew6qswhsczae7@awork3.anarazel.de> <1489276.1674427657@sss.pgh.pa.us> <1708030.1675446770@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1708030.1675446770@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Feb 03, 2023 at 12:52:50PM -0500, Tom Lane wrote: > Andrew Dunstan writes: > > On 2023-01-22 Su 17:47, Tom Lane wrote: > >> Yeah. That's one of my biggest gripes about pgperltidy: if you insert > >> another assignment in a series of assignments, it is very likely to > >> reformat all the adjacent assignments because it thinks it's cool to > >> make all the equal signs line up. That's just awful. > > > Modern versions of perltidy give you much more control over this, so > > maybe we need to investigate the possibility of updating. > > I have no objection to updating perltidy from time to time. I think the > idea is just to make sure that we have an agreed-on version for everyone > to use. Agreed. If we're changing the indentation of assignments, that's a considerable diff already. It would be a good time to absorb other diffs we'll want eventually, including diffs from a perltidy version upgrade.