Comparing Postgres connection pooler support for prepared statements | POSETTE 2024

From the creator

Postgres connection poolers presented by Jelte Fennema-Nio at POSETTE: An Event for Postgres 2024. Connection poolers have always been very important to achieve good performance in transactional workloads with Postgres. Sadly, for a long time this meant that you couldn't use prepared statements to reduce Postgres query planning overhead. But recently that has changed because prepared statements are now supported by PgBouncer, Odyssey, pgcat, and Supavisor. In this talk you'll learn about the differences in prepared statement design, performance, and support between these connection poolers. If you're interested in the answers to one of the following questions, then this is the talk for you: How a connection pooler can be useful when you are using Postgres? Which connection pooler to choose? Technical details about why Postgres prepared statements are so difficult for connection poolers Jelte is currently working on Citus, Postgres and Pgbouncer at Microsoft. Before that he was a big time Postgres user at Stream, where he worked on low latency APIs for chat and social timelines. He is one of the current maintainers of the PgBouncer project. Jelte studied at the University of Amsterdam where he received his BSc in Computer Science and MSc in System and Network Engineering. Chapters: 00:00 - Intro 00:42 - What are connection poolers? 02:17 - What are prepared statements? 04:03 - Why is it difficult with transaction pooling? 06:03 - What options are there? 09:01 - Time to opt

Published 2024-06-13 · Watch on YouTube ↗
Availability and playback restrictions are controlled by the original channel.