Re: [PATCH] seg: preserve the upper boundary's certainty indicator in seg_out()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Ewan Young <kdbase(dot)hack(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] seg: preserve the upper boundary's certainty indicator in seg_out()
Date: 2026-06-12 19:02:42
Message-ID: 1652328.1781290962@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-06-12 19:13:52 Re: Do quoting more carefully in replication commands
Previous Message Andrew Dunstan 2026-06-12 18:58:52 Re: [PATCH] seg: preserve the upper boundary's certainty indicator in seg_out()