Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Date: 2022-03-03 13:16:13
Message-ID: ea4a30ed-c87b-fa84-9668-b0c1cea60304@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 3/3/22 00:03, Michael Paquier wrote:
>>> +if ( (defined($ENV{olddump}) && !defined($ENV{oldinstall}))
>>> + || (!defined($ENV{olddump}) && defined($ENV{oldinstall})))
>> Odd indentation. Spaces between parens?
> Well, perltidy tells me that this is right.
>
>

Yeah, I haven't found a way to make it stop doing that :-(

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2022-03-03 13:18:14 Re: Problem with moderation of messages with patched attached.
Previous Message Masahiko Sawada 2022-03-03 13:02:49 Re: Add the replication origin name and commit-LSN to logical replication worker errcontext