| 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> |
| Subject: | Re: [PG19] eager aggregation gives wrong results because of bpchar_ops |
| Date: | 2026-10-06 23:14:38 |
| Message-ID: | CAH2-Wzk-oO3HjLaByo8Vpse6Tpha1mqAW8DFShh-kS-Wo59ugA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 6, 2026 at 3:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-10-06 23:28:20 | Re: [PG19] eager aggregation gives wrong results because of bpchar_ops |
| Previous Message | surya poondla | 2026-10-06 23:11:33 | Re: pg_walinspect: add functions to locate and list WAL by time and LSN |