Postgres FM
Read-only considerations
This episode isn’t summarized yet
Create a free account and summarize it. In a few minutes you’ll have the key takeaways and a section-by-section summary.
Show notes
Nikolay and Michael discuss a listener request — special considerations for databases that are used in a read-only mode all day, and get an update at night with additional data.
Here are links to a few things we mentioned:
- Index-only scans
- Vacuum
- UK Covid-19 dashboard
- pg_repack
- Partitioning
- Our episode on BRIN indexes
- Always load sorted data (blog post by Haki Benita)
- GIN indexes: the good and the bad (blog post by Lukas Fittl)
- Our episode on materialised views
- pg_buffercache
- Towards Millions TPS (blog post by Alexander Korotkov)
- Postgres WASM (by Snaplet and Supabase)
- Yugabyte
- AWS Aurora
- Continuous Archiving and Point-in-Time Recovery (docs)
- Our episode on checkpoint tuning
- Our episode on partitioning
- PgQ
- Neon branching
- Database Lab Engine
- Cluster
~~~
What did you like or not like? What should we discuss next time? Let us know on social media, or by commenting on our Google doc.
If you would like to share this episode, here's a good link (and thank you!)
~~~
Postgres FM is brought to you by:
- Nikolay Samokhvalov, founder of Postgres.ai
- Michael Christofides, founder of pgMustard
With special thanks to:
- Jessie Draws for the amazing artwork