.JPG.180x180.jpg "Pavel Tolmachev")
Pavel Tolmachev
PostgresPro
11:00
21 June
45 min
Collapse in query plans. Achieve it and manage it
The more tables are involved with the query, the more difficult it is for the scheduler to choose a suitable execution plan (both time and memory usage increase). How can we "tell" the planner that it is better to connect this pair of tables first, and the rest can be connected later? What if we see that a part of our query can be improved, but the optimizer does not do this. In my presentation, I will talk about managing the order of connections. I will explain how we can influence the formation of a query plan using the standard "vanilla" PostgreSQL methods.