Re: Surprising optimizer behavior with a subquery, a GROUP BY, and a range filter - Mailing list pgsql-performance

From Tom Lane
Subject Re: Surprising optimizer behavior with a subquery, a GROUP BY, and a range filter
Date
Msg-id 267807.1767386789@sss.pgh.pa.us
Whole thread Raw
In response to Surprising optimizer behavior with a subquery, a GROUP BY, and a range filter  (wotq <wotq@wotq.dev>)
List pgsql-performance
wotq <wotq@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



pgsql-performance by date:

Previous
From: wotq
Date:
Subject: Surprising optimizer behavior with a subquery, a GROUP BY, and a range filter
Next
From: Mark Kirkwood
Date:
Subject: Unexpected planner choice in simple JOIN