Scalability Limits From SLRU & Lock Manager | Scaling Postgres 306

To get the show notes as well as get notified of new episodes, visit:
www.scalingpostgres.com/episo...
In this episode of Scaling Postgres, we discuss how the SLRU cache and LWLock:LockManager set scalability limits for Postgres, a new release of PgBouncer, and different transaction isolation levels.
Want to learn more about Postgres performance?
Join my FREE mini-course called the PostgreSQL Performance Starter Kit here: www.scalingpostgres.com/cours...
Timestamps:
00:00 - Intro
00:16 - Postgres Indexes, Partitioning and LWLock:LockManager Scalability
04:54 - Waiting for Postgres 17: Configurable SLRU cache sizes for increased performance
06:42 - PgBouncer 1.22.1
07:20 - Isolation Anomalies in PostgreSQL
09:56 - Rails + Postgres
10:34 - Psycopg2 vs Psycopg3 Performance Benchmark
11:23 - CloudNativePG Recipe 1 - Setting up your local playground in minutes
11:45 - Tips for tuning Postgres LIKE & ILIKE queries via pg_trgm on Azure
12:36 - Why I Love psql - PostgreSQL Terminal.
12:57 - Comparing Postgres Managed Services: AWS, Azure, GCP and Supabase
13:25 - PGSQL Phriday #016: Tuning That One Big Query
14:02 - Outro
#postgres #postgresql

[@jaimeduncan6167]

The worst part of the scalability issue is that if "If the day comes on the eve" it has been years since they have done nothing on interact indexes, in fact, they rejected the development even when Alvaro Herrera showed performance gains of 3x and wal generation advantage above 4x. The xid are still 32 bits by the way, in a day and age where many architectures have already or are preparing to drop 32 bit support (not numbers, clearly, architecture). The situation with the stubborn attitude remembers me of the dead or Perl.