Postgres Sort Instability? | Scaling Postgres 322
Join Over 1,000 Engineers & Get New Episodes Weekly!
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.
Content Discussed
- PostgreSQL Sort estimation instability
- Should we use foreign keys?
- Making the PostgreSQL visibility map visible
- Understanding VACUUM, VACUUM template0, and Transaction ID Wraparound
- Custom ENUM Type Columns and ORDER BY
- Post-mortem - Postgres "out of shared memory" error
- Mentoring Program for Code Contributors
- call for applications: mentoring program for code contributors
- Crunchy Data PostgreSQL 16 Security Technical Implementation Guide Released by DISA
- POC: Distributing Trunk Binaries via OCI
- POC: PGXN Binary Distribution Format
- When I grow up I want to be a Database Administrator (said no-one ever)
- Generated Columns in PostgreSQL
- Kubernetes Just Turned Ten: Where Does PostgreSQL Stand?
- Use Open-Source LLMs in PostgreSQL With Ollama and Pgai
- Data Normalization Tips: How to Weave Together Public Datasets to Make Sense of the World
- pg_dump and –if-exists little gem
- Sqlc: 2024 check in
- Generate Vector Tiles with PostGIS
- PostgreSQL performance with different compilers
- Compiling Postgres with LLVM
- Derk van Veen
- Ensuring Safe Data Modifications in PostgreSQL with SELECT FOR UPDATE
- Upgrading to the New Etcd Version From 3.3 for Patroni
- PGConf.dev 2024
- Prague PostgreSQL Developer Day 2024 conference recap
- Alternatives to RDS
YouTube Video
Podcast Audio
