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: | 2025-01-09 09:27:06 |
Message-ID: | CAMbWs4_2T25cEnptbHHLVO2Dw-jwDaLsjK+72WJ18jrw75V2mw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 9, 2025 at 12:15 PM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> hi.
> in create_grouping_expr_infos
>
> tce = lookup_type_cache(exprType((Node *) tle->expr),
> TYPECACHE_BTREE_OPFAMILY);
> if (!OidIsValid(tce->btree_opf) ||
> !OidIsValid(tce->btree_opintype))
> return;
> ....
> /*
> * Get the operator in the btree's opfamily.
> */
> eq_op = get_opfamily_member(tce->btree_opf,
> tce->btree_opintype,
> tce->btree_opintype,
> BTEqualStrategyNumber);
> if (!OidIsValid(eq_op))
> return;
> eq_opfamilies = get_mergejoin_opfamilies(eq_op);
> if (!eq_opfamilies)
> return;
> btree_opfamily = linitial_oid(eq_opfamilies);
>
>
> If eq_op is valid, then we don't need to call get_mergejoin_opfamilies?
> since get_mergejoin_opfamilies output will be the same as tce->btree_opf.
> and we already checked (tce->btree_opf) is valid.
>
> In other words, I think eq_op is valid imply
> that tce->btree_opf is the value (btree opfamily) we need.
Nice catch! Actually, we can use tce->btree_opf directly, without
needing to check its equality operator, since we know it's a btree
opfamily and it's valid. If it were a different opfamily (such as a
hash opfamily), we would need to look up its equality operator, and
select some btree opfamily that that operator is part of. But in this
case, that's not necessary.
Thanks
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | Jakub Wartak | 2025-01-09 09:28:05 | Re: Windows pg_basebackup unable to create >2GB pg_wal.tar tarballs ("could not close file: Invalid argument" when creating pg_wal.tar of size ~ 2^31 bytes) |
Previous Message | Shubham Khanna | 2025-01-09 09:16:05 | Re: Log a warning in pg_createsubscriber for max_slot_wal_keep_size |