Re: [PG19] eager aggregation gives wrong results because of bpchar_ops - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Date
Msg-id 1437400.1791314150@sss.pgh.pa.us
Whole thread
In response to Re: [PG19] eager aggregation gives wrong results because of bpchar_ops  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
List pgsql-hackers
Peter Geoghegan <pg@bowt.ie> writes:
> Attached are lightly edited versions of Shihao Zhong's bug fix
> patches, incorporating the revisions I agreed to earlier today.

> Note again that the patch that's intended for the released back
> branches deliberately ignores the oidvector issue. Also, there are no
> changes to system catalog contents on released branches (just 19 and
> master), which isn't how Noah's similar 2023 interval_ops commit did
> things. Shihao followed that precedent, but I don't think it's
> appropriate to change the contents of the catalogs that initdb
> creates, unless it's truly unavoidable.

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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Manu
Date:
Subject: Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators
Next
From: Antonin Houska
Date:
Subject: Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes