agora inbox for pgsql-committers@postgresql.org  
help / color / mirror / Atom feed
pgsql: Adjust cross-version upgrade tests for seg_out() fix
6+ messages / 1 participants
[nested] [flat]

* pgsql: Adjust cross-version upgrade tests for seg_out() fix
@ 2026-06-12 22:07 Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 6+ messages in thread

From: Andrew Dunstan @ 2026-06-12 22:07 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3e3d7875e95621b02311ea3443e5139e3bce944a

Modified Files
--------------
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | 8 ++++++++
1 file changed, 8 insertions(+)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Adjust cross-version upgrade tests for seg_out() fix
@ 2026-06-12 22:07 Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 6+ messages in thread

From: Andrew Dunstan @ 2026-06-12 22:07 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_18_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/10e510423dc3a0e3c696b981b4d12096c5ab6428

Modified Files
--------------
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | 8 ++++++++
1 file changed, 8 insertions(+)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Adjust cross-version upgrade tests for seg_out() fix
@ 2026-06-12 22:07 Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 6+ messages in thread

From: Andrew Dunstan @ 2026-06-12 22:07 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c0d44e00940672c55c56344f4f3b3ed16b555b01

Modified Files
--------------
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | 8 ++++++++
1 file changed, 8 insertions(+)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Adjust cross-version upgrade tests for seg_out() fix
@ 2026-06-12 22:07 Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 6+ messages in thread

From: Andrew Dunstan @ 2026-06-12 22:07 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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(+)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Adjust cross-version upgrade tests for seg_out() fix
@ 2026-06-12 22:07 Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 6+ messages in thread

From: Andrew Dunstan @ 2026-06-12 22:07 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/8aede3600c84db3d66966ce78a13013911bb2619

Modified Files
--------------
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | 8 ++++++++
1 file changed, 8 insertions(+)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Adjust cross-version upgrade tests for seg_out() fix
@ 2026-06-12 22:07 Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 0 replies; 6+ messages in thread

From: Andrew Dunstan @ 2026-06-12 22:07 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

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_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/7974f94a02a1b39d7c84737ced41890386aaae67

Modified Files
--------------
src/test/perl/PostgreSQL/Test/AdjustUpgrade.pm | 8 ++++++++
1 file changed, 8 insertions(+)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2026-06-12 22:07 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-06-12 22:07 pgsql: Adjust cross-version upgrade tests for seg_out() fix Andrew Dunstan <andrew@dunslane.net>
2026-06-12 22:07 pgsql: Adjust cross-version upgrade tests for seg_out() fix Andrew Dunstan <andrew@dunslane.net>
2026-06-12 22:07 pgsql: Adjust cross-version upgrade tests for seg_out() fix Andrew Dunstan <andrew@dunslane.net>
2026-06-12 22:07 pgsql: Adjust cross-version upgrade tests for seg_out() fix Andrew Dunstan <andrew@dunslane.net>
2026-06-12 22:07 pgsql: Adjust cross-version upgrade tests for seg_out() fix Andrew Dunstan <andrew@dunslane.net>
2026-06-12 22:07 pgsql: Adjust cross-version upgrade tests for seg_out() fix Andrew Dunstan <andrew@dunslane.net>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox