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

From Tom Lane
Subject Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Date
Msg-id 1769161.1791330556@sss.pgh.pa.us
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
I wrote:
> Peter Geoghegan <pg@bowt.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Next
From: Peter Geoghegan
Date:
Subject: Re: [PG19] eager aggregation gives wrong results because of bpchar_ops