upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-06-13 10:40:09 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Adjust cross-version upgrade tests for seg_out() fix

Browse source 
Commit 0e1f1ed157 taught seg_out() to print the certainty indicator
on an interval's upper boundary, but it was back-patched only as far
as v14.  When upgrading from an older release, the old server prints
the one test_seg row exercising that case ('4.6 .. ~7.0') without the
indicator, so the pre- and post-upgrade dumps do not match.  Make
AdjustUpgrade.pm delete just that row; seg's comparison function does
distinguish the certainty indicators, so the otherwise identical row
'4.6 .. 7.0' is unaffected.

Back-patch to all supported branches.

Per buildfarm members crake and fairywren.

Discussion: https://postgr.es/m/5ccbdbde-6467-4a10-bf4d-0be73a05ce8d@dunslane.net
This commit is contained in:
Andrew Dunstan 2026-06-12 18:05:25 -04:00
parent 8bcabfccea
commit c0d44e0094
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm
View file

@ -157,6 +157,14 @@ sub adjust_database_contents
'drop function if exists public.putenv(text)',
'drop function if exists public.wait_pid(integer)');
}
# delete seg row that pre-14 was printed incorrectly but would now
# be printed correctly
if ($dbnames{contrib_regression_seg})
{
_add_st($result, 'contrib_regression_seg',
"delete from test_seg where s = '4.6 .. ~7.0'");
}
}
# user table OIDs are gone from release 12 on