Overhead of pg_stat_statements | Scaling Postgres 304

In this episode of Scaling Postgres, we discuss whether the future of MySQL is Postgres, how to use recursive CTEs, work on OrioleDB, and PG17 performance improvements. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/313-the-future-of-mysql-is-postgres/  

In this episode of Scaling Postgres, we cover potential features in Postgres 17 such as explain serialize, verbose copy, pg_buffer_cache_evict, as well as many others. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/312-postgres-17-commit-orama/  

In this episode of Scaling Postgres, we discuss a 1,400 times faster max and group by implementation, new quantization capabilities in pgvector, adaptive radix trees and splitting & merging partitions in PG17. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/311-max-group-by-performance/  

In this episode of Scaling Postgres, we discuss whether Postgres will pull a Redis, remembering Simon Riggs, built-in collation provider and C.UTF-8 in PG 17 and health checks. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/310-andres-microsoft-postgres-save-linux/  

In this episode of Scaling Postgres, we discuss whether Postgres will pull a Redis, remembering Simon Riggs, built-in collation provider and C.UTF-8 in PG 17 and health checks. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/309-will-postgres-pull-a-redis/  

In this episode of Scaling Postgres, we discuss high availability's future, a custom sharding solution by Figma, sharding pg_vector queries, and PG17 logical replication failover. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/308-scale-through-sharding/  

In this episode of Scaling Postgres, we discuss whether we should be using bytewise or linguistic ordering by default, how to transform data in Postgres, benefits of a transaction_timeout and how to enforce join order. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/307-collation-conundrum/  

In this episode of Scaling Postgres, we discuss one configuration change that resulted in an 11,000 times faster query, why Postgres is not using your index, backported PG improvements and parallelism with TOAST. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/306-scalability-limits-from-slru-lock-manager/  

In this episode of Scaling Postgres, we discuss one configuration change that resulted in an 11,000 times faster query, why Postgres is not using your index, backported PG improvements and parallelism with TOAST. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/305-11k-faster-configuration-change/  

In this episode of Scaling Postgres, we discuss new Postgres releases, performance comparisons between PgBouncer, PgCat and Supavisor, a new extension pg_analytics, and new planner capabilities in PG16. To get the show notes as well as get notified of new episodes, visit:  https://www.scalingpostgres.com/episodes/304-overhead-of-pg_stat_statements/