Scaling Postgres

A podcast by Creston Jamison - Sundays

Sundays

Categories:

167 Episodes

  1. Postgres Sort Instability? | Scaling Postgres 322

    Published: 6/30/2024
  2. Ottertune Is Dead! | Scaling Postgres 321

    Published: 6/23/2024
  3. 100 TB and Beyond! | Scaling Postgres 320

    Published: 6/16/2024
  4. When Postgres Development Stopped! | Scaling Postgres 319

    Published: 6/9/2024
  5. Postgres 17 Beta 1 Released | Scaling Postgres 318

    Published: 6/2/2024
  6. Time-Series Open Source Extension | Scaling Postgres 317

    Published: 5/26/2024
  7. New Releases & 1,000 Times Faster Query | Scaling Postgres 316

    Published: 5/19/2024
  8. Hacking On Postgres is Hard! | Scaling Postgres 315

    Published: 5/12/2024
  9. 150 Times Faster pgvector? | Scaling Postgres 314

    Published: 5/5/2024
  10. The Future of MySQL is Postgres? | Scaling Postgres 313

    Published: 4/28/2024
  11. Postgres 17 Commit-orama | Scaling Postgres 312

    Published: 4/21/2024
  12. 1,400 Times Faster Max & Group By Performance | Scaling Postgres 311

    Published: 4/14/2024
  13. Andres, Microsoft & Postgres Save Linux? | Scaling Postgres 310

    Published: 4/7/2024
  14. Will Postgres Pull A Redis? | Scaling Postgres 309

    Published: 3/31/2024
  15. Scale Through Sharding | Scaling Postgres 308

    Published: 3/24/2024
  16. Collation Conundrum | Scaling Postgres 307

    Published: 3/17/2024
  17. Scalability Limits From SLRU & Lock Manager | Scaling Postgres 306

    Published: 3/10/2024
  18. 11K Faster Configuration Change | Scaling Postgres 305

    Published: 3/3/2024
  19. Overhead of pg_stat_statements | Scaling Postgres 304

    Published: 2/25/2024
  20. PgBouncer, PgCat, Supavisor Fight!!! | Scaling Postgres 303

    Published: 2/18/2024

2 / 9

Learn how to get the best performance and scale your PostgreSQL database with our weekly shows. Receive the best content curated from around the web. We have a special focus on content for developers since your architecture and usage is the key to getting the most performance out of PostgreSQL.