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:35:40
Message-ID: 1681257.1791329740@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> 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.

However, even once that updates, we're going to have some problems.
Trying it locally, I see my animal complaining about updates from
REL_13_STABLE failing, which is unsurprising ... but how do we get
v13-or-before data into a shape that the patched code will accept?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-10-06 23:37:57 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Previous Message Tom Lane 2026-10-06 23:28:20 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops