Re: pg_createsubscriber TAP test wrapping makes command options hard to read.

From: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>
To: "Euler Taveira" <euler(at)eulerto(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Smith" <smithpb2250(at)gmail(dot)com>, "Michael Paquier" <michael(at)paquier(dot)xyz>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Peter Eisentraut" <peter(at)eisentraut(dot)org>, "Euler Taveira" <euler(dot)taveira(at)enterprisedb(dot)com>
Subject: Re: pg_createsubscriber TAP test wrapping makes command options hard to read.
Date: 2025-01-21 01:22:53
Message-ID: 87ikq93qqa.fsf@wibble.ilmari.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Euler Taveira" <euler(at)eulerto(dot)com> writes:

> On Mon, Jan 20, 2025, at 7:49 PM, Tom Lane wrote:
>> "Euler Taveira" <euler(at)eulerto(dot)com> writes:
>> > It is kind of annoying to keep version 20230309 around to run perltidy. Do we
>> > have any other alternatives?
>>
>> As it says in src/tools/pgindent/README:
>>
>> 2) Install perltidy. Please be sure it is version 20230309 (older and newer
>> versions make different formatting choices, and we want consistency).
>>
>> I don't think anyone is especially wedded to 20230309 in particular,
>> but we don't want different developers using different versions and
>> coming out with different results. The whole point of this effort
>> is to standardize code layout as best we can, so that would be
>> counterproductive.
>
> I can live with that.
>
>> Do you have a strong argument for switching to some other specific
>> version of perltidy?
>>
>
> I don't. Let's see if the Dagfinn's patch will maintain more stable formatting
> over the years. I tested in a previous version (20220613) after applying the
> patch and it didn't suggest changes.

More interesting than running older versions of perltidy would be
running more recent ones. On top of the perltidy patch upthread, the
current version (20250105) only wants to make a couple of changes to
PostgreSQL::Test::Cluster (attached):

1. A slight change to the indentation of a multi-line ternary
statement. I slightly prefer the old version, but the new one
doesn't bother me either.

2. Ignoring the length of ## no critic comments when breaking lines,
which is a definite improvement for the secondary `package`
statements in the file.

These changes came with Perl::Tidy 20230701, which is the very next
version after the one we're currently using. Subsequent versions have
caused no other changes, with or without my fat comma patch.

All in all, this makes me +0.5 to bumping the required Perl::Tidy
version, and +0.5 on (at least considering) bumping it to the latest
version before the pre-release-branch pgperltidy run.

- ilmari

Attachment Content-Type Size
0001-Run-pgperltidy-with-Perl-Tidy-20250105.patch.nocfbot text/x-diff 1.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeremy Schneider 2025-01-21 01:25:54 Re: New feature request for adding session information to PostgreSQL transaction log
Previous Message Tatsuo Ishii 2025-01-21 01:20:53 Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options