{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Postgres FM","title":"Upgrades","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/c7a6cda9\"></iframe>","width":"100%","height":180,"duration":2418,"description":"Nikolay and Michael discuss major and minor version Postgres upgrades — what they are, how often they come out, and how regularly we should be upgrading.\n \nHere are links to a few things we mentioned: \nPostgres versioning policy \nwhy-upgrade (by depesz)\npostgresqlco.nf (by Ongres)\npostgresql.conf comparison (by Rustproof Labs) \npg_upgrade\nLogical replication \nCHECKPOINT\namcheck\nLocale data changes (e.g. glibc upgrades)\nANALYZE\nUpgrades are hard (summary of panel discussion by Andreas 'ads' Scherbaum)\nspilo\nRecent pgsql hackers discussion about using logical and pg_upgrade together\n\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\nPostgres FM is brought to you by:\nNikolay Samokhvalov, founder of Postgres.ai\nMichael Christofides, founder of pgMustard\n\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}