Re: Extracting cross-version-upgrade knowledge from buildfarm client

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Extracting cross-version-upgrade knowledge from buildfarm client
Date: 2023-01-15 23:38:58
Message-ID: Y8SOks8SgjF3brDy@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jan 15, 2023 at 06:02:07PM -0500, Tom Lane wrote:
> I guess, but it seems like make-work as long as there's just the one
> column.

Well, the query is already written, so I would use that, FWIW.

> I did find that 002_pg_upgrade.pl could load it. I got stuck at
> the point of trying to test things, because I didn't understand
> what the test process is supposed to be for an upgrade from a
> back branch. For some reason I thought that 002_pg_upgrade.pl
> could automatically create the old regression database, but
> now I see that's not implemented.

test.sh did that, until I noticed that we need to worry about
pg_regress from the past branches to be compatible in the script
itself because we need to run it in the old source tree. This makes
the whole much more complicated to maintain, especially with the
recent removal of input/ and output/ folders in the regression tests
:/
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-01-15 23:41:22 Re: The documentation for storage type 'plain' actually allows single byte header
Previous Message Tom Lane 2023-01-15 23:37:16 Re: Extracting cross-version-upgrade knowledge from buildfarm client