Recovery Time, Lost Data, Production Ready, PG16 Highlights | Scaling Postgres 259
Get New Episodes Weekly!
In this episode of Scaling Postgres, we discuss max_wal_size as it relates to recovery time, losing your data with collation changes, getting production ready and highlights coming in Postgres 16.
Content Discussed
- A little more on max_wal_size
- Did Postgres Lose My Data?
- Collations in Postgres
- Is your Postgres ready for production?
- Postgres 16 highlight - File inclusions in pg_hba.conf and pg_ident.conf
- PostgreSQL 16: GENERIC_PLAN option for EXPLAIN and SHELL exit codes for psql
- New old “debug_parallel_query” setting in PostgreSQL 16
- Using postgres_fdw.parameter_name for advanced monitoring with multiple PostgreSQL servers
- The Cognitive Load of Licensing
- Chris Ellis
- Hosting After Heroku With Chris Oliver | Rubber Duck Dev Show 79
YouTube Video
