I learned there are 151 attendees here. I’ve seen only five women in the entirety.
From yesterday:
PostgreSQL 16 and beyond: Postgres 16 will be a beast. So many improvements and features, I have to get the slide deck and circulate it at work. The release notes are one thing, hearing a core developer talk about them is another. We were given inklings as to what’s being discussed for after PG 16… Logical replication improvements, Async I/O for prefetching, partitioning improvements, 64-bit XIDs, more subquery parallelism.
Patroni 3.0: What’s New and Future Plans: Citus integration, logical failover slots, and security improvements. I’ve never worked with Patroni. I’m stashing this information away for possible future use.
Logical Replication – handling of large DDLs: There was more complexity in replicating DDL commands than I would have first thought. The corner cases in publishing granularity make it challenging and interesting. This may or may not make it into PG 17.
Visualizing Postgres I/O Performance for Development: I love finding unexpected gems in a conference, and this was one. The speaker, Melanie Plageman, blew me away with being super smart. She’s all over benchmarking and delving into Postgres’s and the OS’s complexities. There’s no hard takeaway for my current work except being a reminder to be wary of assumptions and ready to dive deeper to understand the root causes of performance problems.
Today I’m looking forward to:
- Automating index selection using constraint programming
- The journey towards active-active replication in PostgreSQL
- PostgreSQL is nowhere near ready – 3 new directions to develop PostgreSQL
- Continuous aggregates: A use case of Materialized views
- PgBouncer: Present and Future
Seek Nuance 