Thoughts on PostgreSQL in 2024

This is a great post. As an extension developer myself (pg_bm25), seeing more native support for search-related functionalities that extensions can harness would be really great.<p>I&#x27;m surprised nothing was mentioned around pgBouncer&#x2F;connection pooling. Having more native support for general connection pooling has been a requested feature in Postgres for a while, and many popular DBMS have it built-in. Just how some of what Patroni offer should be better bundled in (as the author argues), I think the same could&#x2F;should be true for pgBouncer

&gt; Logical replication allows the real-time streaming of changes from a database into any system that can understand the PostgreSQL logical replication protocol.<p>My Christmas wish for 2024-2025 is that we have an industry standard format for replication. A simple transform (hopefully) of either WAL or logical replication, that we can feed into backup software, search, analytics, whatever.<p>There&#x27;s something out there that fulfills the duties of Kafka and half a dozen other tools (at least two of which don&#x27;t exist yet due to significant barriers to entry) with about a quarter of the code. We just need to carve it out of the block of marble.

“The document discusses where PostgreSQL is heading in 2024 and beyond. It focuses on three key areas: availability, performance, and developer features. For availability, the author sees logical replication and reducing downtime for upgrades and maintenance as important goals. Performance improvements may come from asynchronous I&#x2F;O, parallel recovery, and maximizing resource usage on large instances. On developer features, priorities include supporting more of the SQL&#x2F;JSON standard and making migration from other databases easier. The author also notes opportunities around PostgreSQL extensions, community building, mentorship, and diversity&#x2F;inclusion. Overall, the community is actively working to improve PostgreSQL in many dimensions.” –Kagi summarizer.

I didn&#x27;t know about extension repositories like <a href="https:&#x2F;&#x2F;database.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;database.dev&#x2F;</a>. What less-known extensions are people here using? I&#x27;m curious because there might be extensions that simplify common tasks in ways I&#x27;m unaware of.

&gt; I’ve even talked to users who have workloads that can only be unavailable for 1s – and while I was initially skeptical, when I heard what the workloads were for, I did agree that 1s was a reasonable requirement for them!<p>What could this be? Some crypto exchange is based on PostgreSQL?<p>I generally don&#x27;t understand this kind of a requirement. Downtime, to me, is inability to have an end to end transaction. During downtime, to me, it is possible to queue writes and cache reads, to some extent.<p>I can understand if there is something in the middle, in the database layer, that needs to happen, but what would it be, that requires sub 1s latency, at that level?

Wondering why nothing is said about compression? For MySQL you have Rocksdb with high ZSTD compression. Is the Postgres solution to just use compressed filesystem like ZFS? I could not find much info when researching Postgress, except for Toast compression, which didn&#x27;t seem very strong.<p>I have a huge DB which would take many TB but now runs on a 500GB footprint. Thanks to Rocksdb&#x2F;MySQL. Pondering a move to Postgress, but seemed like a step down in this regard.

I really need to write up my wishlist for PG into a blog post. There is so much to love about it, but it could be so much more. Would love to see some other table formats like column stores, better hash indexes, and tons of SQL improvements - plus something done about connections so we could have so many more without them being resource hogs or taking a long time to connect. Serverless talking to a database sucks.

Confusing <a href="https:&#x2F;&#x2F;db-engines.com&#x2F;en&#x2F;ranking" rel="nofollow">https:&#x2F;&#x2F;db-engines.com&#x2F;en&#x2F;ranking</a><p>1. Oracle. 2. Oracle MySql 3. Microsoft SQL Server 4. Postgres.<p>The ranking has been constant over Jan 2024, December 2023 and January 2023. So no change.<p>Postgres did have the biggest increased score in Jan 2023, yet the change did not change its position in the ranking.

&gt; building and managing an active-active system is extremely complicated<p>Could Postgres yet evolve to become a Spanner-like multi-writer system?