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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 20:44:25
Message-ID: 3ca625b6-58bf-4847-a388-ebc3758b5704@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2026-06-12 Fr 3:02 PM, Tom Lane wrote:
> 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.
>

WFM, I will work on it.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-06-12 20:44:26 Re: fix prev link in docs
Previous Message Zsolt Parragi 2026-06-12 20:39:27 Re: [PATCH v1] Add ssl_alt_cert_file/ssl_alt_key_file for dual RSA+ECDSA certificate support