Re: [PG19] eager aggregation gives wrong results because of bpchar_ops - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Date
Msg-id CAH2-WzmZXDUWYLpJmU6yXx31wc4xpk86QbiJbQR-bC3SpXevSA@mail.gmail.com
Whole thread
In response to Re: [PG19] eager aggregation gives wrong results because of bpchar_ops  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
List pgsql-hackers
On Tue, Oct 6, 2026 at 7:49 PM Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Clear FatalError earlier during crash restart