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.
Here are some links to things they mentioned:
- Nik’s tweet demonstrating a NOTIFY hot spot https://x.com/samokhvalov/status/1959468091035009245
- Postgres LISTEN/NOTIFY does not scale (blog post by Recall ai) https://www.recall.ai/blog/postgres-listen-notify-does-not-scale
- track_io_timing https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-TRACK-IO-TIMING
- pg_test_timing https://www.postgresql.org/docs/current/pgtesttiming.html
- PlanetScale for Postgres https://planetscale.com/blog/planetscale-for-postgres
- Out of disk episode https://postgres.fm/episodes/out-of-disk
- 100TB episode https://postgres.fm/episodes/to-100tb-and-beyond
- Latency Numbers Every Programmer Should Know https://gist.github.com/jboner/2841832
- Fio https://github.com/axboe/fio
~~~
What 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!
~~~
Postgres FM is produced by:
- Michael Christofides, founder of pgMustard
- Nikolay Samokhvalov, founder of Postgres.ai
With credit to:
- Jessie Draws for the elephant artwork