Hi, On 2025-08-24 09:08:16 -0700, Noah Misch wrote: > On Sun, Aug 24, 2025 at 11:50:01AM -0400, Tom Lane wrote: > > Andres Freund <and...@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.
Ah, ok, that does make it less worthwhile to go after. > > I feel that that's the wrong tradeoff. CI should be expected to be > > fairly cheap, not to catch everything the buildfarm could catch. I think it's also about removing painful manual testing - and imo manually running cross-version pg_upgrade tests is really rather painful. > It can always be non-default, like the mingw test. Indeed. We now have the infrastructure to enable such tests for cfbot while not running by default in user's repositories (which will commonly be more compute constrained). Greetings, Andres Freund
