| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | shihao zhong <zhong950419(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Guofenglinux <guofenglinux(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: [PG19] eager aggregation gives wrong results because of bpchar_ops |
| Date: | 2026-10-06 23:49:16 |
| Message-ID: | 1769161.1791330556@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Peter Geoghegan <pg(at)bowt(dot)ie> writes:
>> By backpatching to REL_13_STABLE? I see no other reasonable way, given
>> the constraints.
> That was my first reaction too, but then what are we testing?
> Nothing corresponding to real-world upgrades.
Actually, we do have a precedent for fixing this: it's to drop
tables or indexes that the newer version gets indigestion on.
See adjust_database_contents in AdjustUpgrade.pm.
I'm about to go to dinner, but I can work on fixing this afterwards
if you don't want to.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2026-10-06 23:54:33 | Re: [PG19] eager aggregation gives wrong results because of bpchar_ops |
| Previous Message | Tom Lane | 2026-10-06 23:41:33 | Re: [PG19] eager aggregation gives wrong results because of bpchar_ops |