Postgres Sort Instability? | Scaling Postgres 322

To get the show notes as well as get notified of new episodes, visit: https://www.scalingpostgres.com/episodes/322-postgres-sort-instability/ In this episode of Scaling Postgres, we discuss an incremental sort instability issue with the Postgres planner, whether we should use foreign keys, how the visibility map works and how to vacuum the template0 database. Want to learn more about Postgres performance? Join my FREE training called Postgres Performance Demystified here: https://www.scalingpostgres.com/courses/postgres-performance-demystified/ Timestamps: 00:00 - Intro 00:48 - PostgreSQL Sort estimation instability 04:15 - Postgres Performance Demystified 04:49 - Should we use foreign keys? 07:09 - Making the PostgreSQL visibility map visible 11:28 - Understanding VACUUM, VACUUM template0, and Transaction ID Wraparound 13:35 - Custom ENUM Type Columns and ORDER BY 15:06 - Post-mortem - Postgres "out of shared memory" error 16:35 - Mentoring Program for Code Contributors 16:58 - call for applications: mentoring program for code contributors 17:58 - Crunchy Data PostgreSQL 16 Security Technical Implementation Guide Released by DISA 18:22 - POC: Distributing Trunk Binaries via OCI 18:42 - POC: PGXN Binary Distribution Format 18:53 - When I grow up I want to be a Database Administrator (said no-one ever) 19:23 - Outro #postgres #postgresql