Re: [PATCH] Fix pg_upgrade test from v10

From: "Anton A(dot) Melnikov" <aamelnikov(at)inbox(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Fix pg_upgrade test from v10
Date: 2022-07-31 22:04:39
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 06.07.2022 08:58, Michael Paquier wrote:

> That's the kind of things I already proposed on this thread, aimed at
> improving the coverage, and this takes care of more issues than what's
> proposed here:
> I'll rebase my patch to include fixes for --wal-segsize and
> --allow-group-access when using versions older than v11.
> --
> Michael

I looked at this thread and tried to apply some changes from it in practice.
And found one strange error and describe it in a comment here:
It would be interesting to know if it occures on
my PC only or somewhere else.

On 05.07.2022 22:08, Justin Pryzby wrote:
> ..since it tries to apply all the *.patch files to the master branch, one after
> another. For branches other than master, I suggest to name the patches *.txt
> or similar. Or, just focus for now on allowing upgrades *to* master. I'm not
> sure if anyone is interested in patching in backbranches. I'm not
> sure, but there may be more interest to backpatch the conversion to TAP
> (322becb60).

Yes, the backport idea seems to be interesting. I wrote more about this in a new thread:
as the current topic has nothing to do with the backport of TAP tests.

With best regards,
Anton A. Melnikov
Postgres Professional:
The Russian Postgres Company

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2022-07-31 22:07:32 Re: ci: update to freebsd 13.1 / remove minor versions from image names
Previous Message Anton A. Melnikov 2022-07-31 22:02:21 [PATCH] Backport perl tests for pg_upgrade from 322becb60