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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
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:28:20
Message-ID: 1644081.1791329300@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> 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.

Yeah, it's visibly run 19 and HEAD before the older branches, which
seems odd. Usually the BF client does the branches back-to-front.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-10-06 23:35:40 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Previous Message Peter Geoghegan 2026-10-06 23:14:38 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops