Scaling Postgres Episode 240 Forced Sequential Scans, Table Renaming, Terminology, PGSQL Phriday

In this episode of Scaling Postgres, we discuss how sequential scans can be forced, the best way to rename a table without downtime, different Postgres terminology and the PGSQL Phriday blogging event.

Content Discussed

• Forcing Sequential Scans on PostgreSQL Using Large Integers
• 5mins of Postgres E42: A surprising case of very large integers causing a Sequential Scan
• Postgres: Safely renaming a table with no downtime using updatable views
• Postgres Insider Terminology
• PGSQL Phriday #002: PostgreSQL Backup and Restore
• Backups for Postgres - PGSQL Phriday #002
• How to do proper backups
• Validating Backups: PGSQL Phriday #002
• Adventures in PostgreSQL Backups
• pg_basebackup could not set compression worker count - unsupported parameter
• btree vs. BRIN: 2 options for indexing in PostgreSQL data warehouses
• Postgres Indexing: When Does BRIN Win?
• New Public Schema Permissions in PostgreSQL 15
• PostgreSQL: Are All NULLs the Same?
• Securing Patroni REST API End Points – Part 1
• Data Loading in Postgres for Newbies
• Version control for databases
• Adrien Nayrat
• Rubber Duck Dev Show Episode 64 | Where To Put Your Business Logic With Jason Charnes

YouTube Video