| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Adjust cross-version upgrade tests for seg_out() fix |
| Date: | 2026-06-12 22:07:51 |
| Message-ID: | E1wYA2Z-0004JP-0O@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Adjust cross-version upgrade tests for seg_out() fix
Commit 0e1f1ed157e 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
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d266413293462334b12d387ca826a8d65c955691
Modified Files
--------------
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | 8 ++++++++
1 file changed, 8 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2026-06-14 01:13:50 | pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple |
| Previous Message | Andrew Dunstan | 2026-06-12 14:31:43 | pgsql: Don't try to import a non-exported object in vcregress.pl |