Re: Surprising optimizer behavior with a subquery, a GROUP BY, and a range filter

[Tom Lane]

wotq <w...@wotq.dev> writes:
> The following query isn't optimized as I would expect:

I don't see this misbehavior on HEAD or v18 branch tip.  I suspect
it was fixed last week by [1] and/or [2].

                        regards, tom lane

[1] https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=ad66f705f
[2] https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=559f9e90d