Postgres Planner Quirks: JOIN Equivalence Classes and IN/ANY filters
Find the article on our blog here:
https://pganalyze.com/blog/5mins-post...
In E117 of "5mins of Postgres" we continue our series on Postgres planner quirks. In this episode we discuss JOIN column equivalence and when there are issues with IN/ANY filters not being considered as part of the equivalence class in Postgres.
Learn more about pganalyze:
https://pganalyze.com
https://pganalyze.com/newsletter
/ pganalyze
Check out the pganalyze library for eBooks, webinars, and more:
https://pganalyze.com/resources
📑 What we have discussed in this episode of 5mins of Postgres:
Optimizing Performance in PostgreSQL: Join Column and ANY Filters - Blog post by Deepak Mahto
https://databaserookies.wordpress.com...
Parameterized Index Scans, or: Why Nested Loop are sometimes a good join type - Blog post on pganalyze blog
https://pganalyze.com/blog/how-postgr...
Internal Postgres Planner ("optimizer") documentation on Equivalence Classes
https://github.com/postgres/postgres/...
Condition pushdown: why (=) is pushed down into join, but BETWEEN or larger equals is not? - Discussion on pgsql-hackers mailinglist
https://www.postgresql.org/message-id...
Equivalence Class Filters - Patch in 2022 Postgres Commitfest
https://commitfest.postgresql.org/37/...
#postgres #postgresql #queryoptimization