Advanced EXPLAIN | Postgres.FM 118 |

[ 🇬🇧_🇺🇸 Check out the subtitles - we now edit them, ChatGPT+manually! You can also try UA-cam's auto-translation of them from English to your language; try it and share it with people interested in Postgres!]
Nikolay and Michael discuss some more advanced topics around EXPLAIN, including some tips for complex query plans, some recent improvements, and an idea or two that might make it even better.
Here are some links to things they mentioned:
Michael’s solo episode on the basics of EXPLAIN postgres.fm/ep...
Our episode on auto_explain postgres.fm/ep...
Which cloud providers support auto_explain? (Blog post by Michael) www.pgmustard....
psychopg www.psycopg.org
Our first episode on BUFFERS postgres.fm/ep...
Our second episode on BUFFERS postgres.fm/ep...
track_io_timing www.postgresql...
compute_query_id www.postgresql...
EXPLAIN: beyond the basics (talk by Michael) • EXPLAIN: beyond the ba...
~~~
What did you like or not like? What should we discuss next time? Let us know in the comments, or by tweeting us on @postgresfm / postgresfm , @samokhvalov / samokhvalov and @michristofides / michristofides
~~~
Postgres FM is produced by:
Nikolay Samokhvalov, founder of Postgres.ai postgres.ai/
Michael Christofides, founder of pgMustard pgmustard.com/
~~~
This is the video version. Check out postgres.fm to subscribe to the audio-only version, to see the transcript, guest profiles, and more.

[@obacht7]

Thank you Michael and Nikolay for another interesting episode. Only through your explanation I realized that partition elimination cannot happen for prepared statements during the planning phase when query parameters are involved in the pruning operation. This seems trivial in hindsight, but valueable to remember. I think no RDBMS can work around that barrier.

[@wstrzalka]

+1 to your VERBOSE proposal Michael