| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tender Wang <tndrwang(at)gmail(dot)com>, Paul George <p(dot)a(dot)george19(at)gmail(dot)com>, Andy Fan <zhihuifan1213(at)163(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Eager aggregation, take 3 |
| Date: | 2024-10-29 07:56:56 |
| Message-ID: | CAMbWs4_0UavnJdCFwMX1GZVYvaH_7PGVZbHO9-Y0tFa4PvssZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 18, 2024 at 10:22 PM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> So overall I doubt here BTEQUALIMAGE_PROC flag usage is correct.
The BTEQUALIMAGE_PROC flag is used to prevent eager aggregation for
types whose equality operators do not imply bitwise equality, such as
NUMERIC.
After a second thought, I think it should be OK to just check the
equality operator specified by the SortGroupClause for btree equality.
I’m not very sure about this point, though, and would appreciate any
inputs.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2024-10-29 07:59:04 | RE: Conflict detection for update_deleted in logical replication |
| Previous Message | Bertrand Drouvot | 2024-10-29 07:54:24 | Re: define pg_structiszero(addr, s, r) |