Re: Test instability when pg_dump orders by OID - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Test instability when pg_dump orders by OID
Date
Msg-id 20250824160816.06.nmisch@google.com
Whole thread Raw
In response to Re: Test instability when pg_dump orders by OID  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Aug 24, 2025 at 11:50:01AM -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > I wonder if it's worth adding support to CI to perform the cross-version
> > upgrade test. It'd be pretty easy to install all pgdg apt postgres packages to
> > the debian image, which then could be used as the source version...

I think catching this particular case would take more than that.  It entails
running the latest v16 src/test/regress suite, capturing the dump of that into
$animal_root/upgrade.$animal/REL_16_STABLE/*.sql, and seeing the upgrade
failure of that dump having the latest v16 regression objects.  I don't know
how to get there without a v16 source tree.

> I feel that that's the wrong tradeoff.  CI should be expected to be
> fairly cheap, not to catch everything the buildfarm could catch.

It can always be non-default, like the mingw test.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Test instability when pg_dump orders by OID
Next
From: Andrew Dunstan
Date:
Subject: Re: Non-text mode for pg_dumpall