Re: BUG #19517: Eager Aggregation produces wrong count(*) when pushed into RHS of Hash Semi Join

Поиск
Список
Период
Сортировка
Искать

Re: BUG #19517: Eager Aggregation produces wrong count(*) when pushed into RHS of Hash Semi Join

От:
Tender Wang <tndrwang@gmail.com>
Дата:
Hi all

Matheus Alcantara  于2026年6月11日周四 04:19写道:
>
> On Wed Jun 10, 2026 at 12:44 PM -03, PG Bug reporting form wrote:
> > Likely cause
> > ------------
> > Eager Aggregation appears to consider the RHS of a SEMI/ANTI join a legal
> > site to push a partial aggregate, but for SEMI joins each outer row matches
> > at most one inner row by the join's own semantics, so partial counts taken
> > on the inner side cannot be combined into a correct outer-side count(*).
> > Either eager aggregation must be disabled for the RHS of SEMI/ANTI joins,
> > or the partial state must be projected through the semi-join such that
> > each surviving outer row contributes exactly one partial.
> >
> > Two follow-up commits to eager aggregation landed on 2026-04-06
> > ("Fix volatile function evaluation in eager aggregation" and
> > "Fix collation handling for grouping keys in eager aggregation"), but
> > neither addresses semi-join correctness.
> >
>
> Wondering if commit ffeda04259b (Fix eager aggregation for semi/antijoin
> inner rels) is about fixing this issue. Can you please check it? I think
> that 19beta1 was created before the fix was applied on master.
>

Yes, this commit ffeda04259b has fixed this problem. But it wasn't
included in the 19beta1.
I tried on HEAD, and the result was correct.

postgres=# SELECT u.user_id, count(*)
FROM   u
WHERE  u.value_2 = ANY (SELECT e.value_2
                        FROM   e
                        WHERE  u.user_id > e.user_id)
GROUP BY u.user_id;
 user_id | count
---------+-------
       5 |    26
(1 row)

postgres=# explain SELECT u.user_id, count(*)
FROM   u
WHERE  u.value_2 = ANY (SELECT e.value_2
                        FROM   e
                        WHERE  u.user_id > e.user_id)
GROUP BY u.user_id;
                             QUERY PLAN
---------------------------------------------------------------------
 HashAggregate  (cost=4.76..4.77 rows=1 width=12)
   Group Key: u.user_id
   ->  Hash Semi Join  (cost=3.25..4.71 rows=9 width=4)
         Hash Cond: (u.value_2 = e.value_2)
         Join Filter: (u.user_id > e.user_id)
         ->  Seq Scan on u  (cost=0.00..1.26 rows=26 width=8)
         ->  Hash  (cost=2.00..2.00 rows=100 width=8)
               ->  Seq Scan on e  (cost=0.00..2.00 rows=100 width=8)
(8 rows)





-- 
Thanks,
Tender Wang


pgsql: Remove useless/confusing const qualifiers

От:
Peter Eisentraut <peter@eisentraut.org>
Дата:
Remove useless/confusing const qualifiers

The const qualifiers removed here did not qualify what is being
pointed to, which is the normal use in function prototypes.  Instead,
they qualify the variable itself, so that it cannot be changed inside
the function.  That is itself not wrong, but it's not a normal style,
and it seems distracting here.

Reviewed-by: Chao Li 
Discussion: https://www.postgresql.org/message-id/flat/c855d318-4545-4dc7-b466-2e24fbf64725%40eisentraut.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/370f3366c4c214abb0c34b2e2bd7fd42802112bf

Modified Files
--------------
src/bin/psql/describe.c      | 14 +++++++-------
src/fe_utils/print.c         | 20 ++++++++++----------
src/include/fe_utils/print.h | 18 +++++++++---------
3 files changed, 26 insertions(+), 26 deletions(-)

FAQ