Re: pg_upgrade and cross-library upgrades

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgbf(at)twiska(dot)com
Subject: Re: pg_upgrade and cross-library upgrades
Date: 2023-07-07 12:51:16
Message-ID: D209F8B0-514B-4495-A348-C7FBED800068@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 6 Jul 2023, at 02:19, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Wed, Jul 05, 2023 at 07:03:56AM -0400, Tom Lane wrote:

>> Not entirely sure this is worth the effort.
>
> I am not sure either..

I can't see off the cuff that it would bring better test coverage or find bugs
relative to the effort of making it stable.

> Anyway, the buildfarm code does similar things
> already, see around $bad_module in TestUpgradeXversion.pm, for
> instance. So this kind of workaround exists already. It seems to me
> that we should try to pull that out of the buildfarm code and have
> that in the core module instead as a routine that would be used by the
> in-core TAP tests of pg_upgrade and the buildfarm code.

That however, would be a more interesting outcome.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2023-07-07 12:54:53 RE: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL
Previous Message Ants Aasma 2023-07-07 12:43:14 Re: Disabling Heap-Only Tuples