최적화 장벽을 이용한 Postgres에서의 조인 순서 강제

*Find the article on our blog here:* https://pganalyze.com/blog/5mins-postgres-forcing-join-order

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:*

https://pganalyze.com

https://pganalyze.com/newsletter

https://twitter.com/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:*

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

https://www.cybertec-postgresql.com/en/forcing-a-join-order-in-postgresql/

*pg_hint_plan*

https://pghintplan.osdn.jp/pg_hint_plan.html

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

https://youtu.be/nVhLTwVefCA

*The Basics of Postgres Query Planning*

https://pganalyze.com/docs/explain/basics-of-postgres-query-planning

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

https://pganalyze.com/blog/how-postgres-chooses-index

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

https://pganalyze.com/blog/5mins-postgres-tuning-deterministic-query-planner-extended-statistics-join-collapse-limits

*pg_hint_plan GitHub repository*

https://github.com/ossc-db/pg_hint_plan

*eBook: Effective Indexing in Postgres*

https://pganalyze.com/ebooks/postgres-indexing