Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Date
Msg-id 4f54cd76-756e-ba8e-0238-cacf6dbc971b@enterprisedb.com
Whole thread Raw
In response to Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
List pgsql-hackers
On 03.10.21 09:03, Michael Paquier wrote:
> On Sat, Oct 02, 2021 at 11:34:38PM -0400, Tom Lane wrote:
>> Maybe we could leave test.sh in place for awhile?  I'd rather
>> not cause a flag day for buildfarm owners.  (Also, how do we
>> see this working in the back branches?)
> 
> I would be fine with test.sh staying around for now.

test.sh could be changed to invoke the TAP test.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Skipping logical replication transactions on subscriber side
Next
From: Peter Eisentraut
Date:
Subject: Re: Bug in DefineRange() with multiranges