public inbox for [email protected]
help / color / mirror / Atom feedFrom: Daniel Gustafsson <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Postgres hackers <[email protected]>
Cc: Thomas Munro <[email protected]>
Cc: [email protected]
Subject: Re: pg_upgrade and cross-library upgrades
Date: Fri, 7 Jul 2023 14:51:16 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
> On 6 Jul 2023, at 02:19, Michael Paquier <[email protected]> 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
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: pg_upgrade and cross-library upgrades
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox