Forcing Join Order in Postgres Using Optimization Barriers

In today’s episode 67 of “5mins of Postgres” I want to talk about forcing join order in Postgres. We’ll walk through 3 techniques: Adding OFFSET “0” to a sub-SELECT, using common table expressions, and working with the join_collapse_limit.

*Learn more about pganalyze:*

*Check out the pganalyze library for eBooks, webinars, and more:*

📑 *What we have discussed in this episode of 5mins of Postgres:*

*Forcing a join order in PostgreSQL - by Laurenz Albe*

*pg_hint_plan*

*Webinar Recording: How to use the Postgres query planner to debug bad plans and speed up queries*

*The Basics of Postgres Query Planning*

*How Postgres Chooses Which Index To Use For A Query*

*5mins of Postgres E15: Tuning Postgres' Deterministic Query Planner, Extended Statistics and Join Collapse Limits*

*pg_hint_plan GitHub repository*

*eBook: Effective Indexing in Postgres*