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

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, 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-07 00:52:53
Message-ID: CAGRkXqS104zuoZxFYZ0mD5g1V5y5=USU0hFNQxDmpaq-Bm+HfA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Peter, Tom,

Thanks for pushing this and for taking care of the upgrade test failure.

I was not around when the crake failure came up, so I want to explain.
I work a day job in EST, and I do PostgreSQL work
mostly outside those hours. I usually read the list in the evening, and
a reply from me can take until then. It is not that I am ignoring the
thread.

I saw Peter's 0001-Fix-XversionUpgrade-allequalimage-failures.patch, and
the AdjustUpgrade.pm approach looks right to me. Peter said validating
it is the hard part. Let me try to play with this patch.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-10-07 00:53:40 Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers
Previous Message Tom Lane 2026-10-07 00:50:29 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops