{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Postgres FM","title":"pg_stat_statements","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/e8fb2a4e\"></iframe>","width":"100%","height":180,"duration":2751,"description":"Nikolay and Michael discuss pg_stat_statements — why everyone should use it, but also some downsides!\n \nHere are links to a few things we mentioned: \npg_stat_statements (docs)\npg_stat_statements (PgPedia)\nPGSQL Phriday\nObserver effect in pg_stat_statements and pg_stat_kcache (Postgres Hacking session on Postgres TV) \ntrack_io_timing (docs)\nOverhead comment (by Tom Kate, via Jeremy Schneider) \npg_stat_monitor\nPGCon\nOur episode on query analysis\nMarginalia \n\n~~~\n\nWhat did you like or not like? What should we discuss next time? Let us know on YouTube, on social media, or by commenting on our Google doc.\nIf you would like to share this episode, here's a good link (and thank you!)\n\n~~~\nPostgres FM is brought to you by:\nNikolay Samokhvalov, founder of Postgres.ai\nMichael Christofides, founder of pgMustard\nWith special thanks to:\nJessie Draws for the amazing artwork ","thumbnail_url":"https://img.transistorcdn.com/NFbJlGhGV5mzIU1kM0iZ823A69pjZUNX40LszVO5LKI/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzMyMTQ3LzE3MTA3/OTEzODMtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}