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-Wzk-oO3HjLaByo8Vpse6Tpha1mqAW8DFShh-kS-Wo59ugA@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 3:15 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Patches LGTM.  I could go along with removing those entries from the
> .dat files in the older branches, but not doing so is fine too.

I pushed this, but see a XversionUpgrade-REL_18_STABLE-REL_19_STABLE
buildfarm failure on crake. It looks like crake's amcheck run
correctly complains when a bpchar index is upgraded. This must be due
to it using a stale version of REL_18_STABLE with the latest
REL_19_STABLE.

I imagine that the failure will stop soon, once crake starts using a
REL_18_STABLE with the fix. Does that sound right?

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: surya poondla
Date:
Subject: Re: pg_walinspect: add functions to locate and list WAL by time and LSN
Next
From: Tom Lane
Date:
Subject: Re: [PG19] eager aggregation gives wrong results because of bpchar_ops