Re: pg_upgrade: Make testing different transfer modes easier
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-12-15T08:34:17Z
Lists: pgsql-hackers
> On 15 Dec 2022, at 01:56, Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote:
>
> At Wed, 14 Dec 2022 10:40:45 +0100, Daniel Gustafsson <daniel@yesql.se> wrote in
>>> On 14 Dec 2022, at 08:04, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
>>>
>>> On 07.12.22 17:33, Peter Eisentraut wrote:
>>>> I think if we want to make this configurable on the fly, and environment variable would be much easier, like
>>>> my $mode = $ENV{PG_TEST_PG_UPGRADE_MODE} || '--copy';
>>>
>>> Here is an updated patch set that incorporates this idea.
>
> We have already PG_TEST_EXTRA. Shouldn't we use it here as well?
I think those are two different things. PG_TEST_EXTRA adds test suites that
aren't run by default, this proposal is to be able to inject options into a
test suite to modify its behavior.
--
Daniel Gustafsson https://vmware.com/
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_upgrade: Add --copy option
- 746915c68669 16.0 landed
-
pg_upgrade: Make testing different transfer modes easier
- b059a2409faf 16.0 landed