Re: [PATCH] seg: preserve the upper boundary's certainty indicator in seg_out()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>, Ewan Young <kdbase.hack@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-12T19:02:42Z
Lists: pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes: > This is upsetting cross version upgrade tests, I assume since we didn't > backport it to branches older than 14. > Not sure what the best solution is. Drop the table, or at least the > offending row? I'd vote for teaching AdjustUpgrade.pm to delete just the problematic row. No reason to remove more test surface than we have to. regards, tom lane
Commits
-
Adjust cross-version upgrade tests for seg_out() fix
- 7974f94a02a1 14 (unreleased) landed
- 8aede3600c84 15 (unreleased) landed
- d26641329346 16 (unreleased) landed
- c0d44e009406 17 (unreleased) landed
- 10e510423dc3 18 (unreleased) landed
- 3e3d7875e956 19 (unreleased) landed
-
seg: Fix seg_out() to preserve the upper boundary's certainty indicator
- 58b91fc73a86 14 (unreleased) landed
- b3aa2083a4da 15 (unreleased) landed
- 504ca05133db 16 (unreleased) landed
- bcbbd070d496 17 (unreleased) landed
- 0004cab4dc60 18 (unreleased) landed
- 0e1f1ed157e9 19 (unreleased) landed