{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Postgres FM","title":"Disks","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/dabdc7fa\"></iframe>","width":"100%","height":180,"duration":2773,"description":"Nik and Michael discuss disks in relation to Postgres — why they matter, how saturation can happen, some modern nuances, and how to prepare to avoid issues.\n \nHere are some links to things they mentioned:\nNik’s tweet demonstrating a NOTIFY hot spot https://x.com/samokhvalov/status/1959468091035009245\nPostgres LISTEN/NOTIFY does not scale (blog post by Recall ai) https://www.recall.ai/blog/postgres-listen-notify-does-not-scale\ntrack_io_timing https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-TRACK-IO-TIMING\npg_test_timing https://www.postgresql.org/docs/current/pgtesttiming.html \nPlanetScale for Postgres https://planetscale.com/blog/planetscale-for-postgres\nOut of disk episode https://postgres.fm/episodes/out-of-disk\n100TB episode https://postgres.fm/episodes/to-100tb-and-beyond \nLatency Numbers Every Programmer Should Know https://gist.github.com/jboner/2841832\nFio https://github.com/axboe/fio\n\n~~~\nWhat did you like or not like? What should we discuss next time? Let us know via a YouTube comment, on social media, or by commenting on our Google doc!\n\n~~~\nPostgres FM is produced by:\nMichael Christofides, founder of pgMustard\nNikolay Samokhvalov, founder of Postgres.ai\n\nWith credit to:\nJessie Draws for the elephant 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}