{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Postgres FM","title":"Read-only considerations","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/3b242ada\"></iframe>","width":"100%","height":180,"duration":2390,"description":"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.\nHere are links to a few things we mentioned: \nIndex-only scans\nVacuum\nUK Covid-19 dashboard\npg_repack\nPartitioning\nOur episode on BRIN indexes\nAlways load sorted data (blog post by Haki Benita)\nGIN indexes: the good and the bad (blog post by Lukas Fittl)\nOur episode on materialised views\npg_buffercache\nTowards Millions TPS (blog post by Alexander Korotkov)\nPostgres WASM (by Snaplet and Supabase)\nYugabyte\nAWS Aurora \nContinuous Archiving and Point-in-Time Recovery (docs)\nOur episode on checkpoint tuning\nOur episode on partitioning\nPgQ\nNeon branching\nDatabase Lab Engine\nCluster\n~~~\n\nWhat 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.\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}