Re: [PG19] eager aggregation gives wrong results because of bpchar_ops

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:54:33
Message-ID: CAH2-WzmZXDUWYLpJmU6yXx31wc4xpk86QbiJbQR-bC3SpXevSA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 6, 2026 at 7:49 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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 just found that myself; commit b352d3d8 had to do this.

> I'm about to go to dinner, but I can work on fixing this afterwards
> if you don't want to.

I'll see where I get with following this precedent now.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-10-07 00:07:06 Re: [PATCH] Clear FatalError earlier during crash restart
Previous Message Tom Lane 2026-10-06 23:49:16 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops