Databases in 2025: A Year in Review — Esteemed database expert Andy Pavlo has put together a fantastic look at the major trends and things that went on in the world of databases over the past year. Postgres gets pride of place as the ‘dominant’ database of 2025, but there’s much more to enjoy here.

Andy Pavlo

POSETTE 2026—The Call for Proposals Closes Soon! — New year, new goals! Resolve to share your Postgres insights at POSETTE: An Event for Postgres, a free & virtual developer event organized by the PostgreSQL team at Microsoft—happening June 16–18, 2026. The CFP closes on Feb 1. Get started.

Microsoft sponsor

Postgres Performance: Latency in the Cloud & On-Premise — Having a performant database is one thing, but its location has a big impact on latency — which, if too high, can outweigh everything else performance-wise.

Hans-Jürgen Schönig

Postgres 18's RETURNING Enhancements — Postgres 18 enhanced the RETURNING clause used in DML queries (inserting, updating, etc.) to support old and new aliases to explicitly access the previous and current state of data.

Ahsan Hadi

pg_csv_loader: A Tool for 'Quick and Dirty' Loading of CSV Files — A JavaScript-powered tool for loading CSV files into Postgres databases with minimal configuration needed. Source.

Hubert depesz Lubaczewski

1. Life-Altering Postgres Patterns — The author promised us that the title isn’t just clickbait (although clearly it worked, being at #1!) and delivered twelve different bite-size, hard-learned tips and insights in areas from using UUIDs as primary keys and table naming to the use of schemas and views.

Ethan McCue

2. Don't Do This (in Postgres) — A perennially interesting page on the official Postgres wiki rounding up advice around ‘common mistakes’ in using Postgres and what not to do, like “Don’t use char(n)” and “Don’t use serial“. Some will be contentious, but are backed up with reasons.

Postgres Wiki

3. Kafka is Fast, I'll Use Postgres — Inspired by another post about using Postgres instead of Redis for caching, the author sets out to see if Postgres is good enough to handle use cases for which you might naturally choose Kafka.

Stanislav Kozlovski

4. How to Fix a Common Cause of Slow Queries in Postgres — A database engineer at Render shows off a commonly encountered, but trivially fixed, performance issue caused by missing indexes on foreign keys.

Eric Fritz

5. Lessons from Scaling Postgres Queues to 100K Events Per Second — RudderStack decided to use Postgres as their main queueing system rather than something like Kafka and their team shares the story of what they learned.

Aris Tzoumas (RudderStack)

6. Benchmarking Postgres 17 vs 18 — The author conducted a series of detailed performance benchmarks between Postgres 17 and 18, in some 96 combinations, and reassuringly finds that Postgres 18 provides a nice performance bump, that local disks rule, and tweaking your settings remains worthwhile.

Ben Dicken (PlanetScale)

7. 1 Trillion Rows in Citus? — “Postgres scales,” but just how far does that go? Hans-Jürgen decided to find out, running a little (or is it big?) experiment to see if a 1 trillion row table is even achievable.

Hans-Jürgen Schönig

8. Just Because You’re Getting an Index Scan, Doesn't Mean You Can’t Do Better — If you see index scans when reviewing query plans, you might think you’re on the right path to a high performing query, but there’s more juice left for the squeezing, says Michael.

Michael Christofides

9. Pipelining Comes to psql in Postgres 18 — psql in Postgres 18 and later is equipped with commands to use pipelining in SQL scripts, something Daniel notes “can provide huge gains in query throughput”.

Daniel Vérité

10. Postgres in the Time of Monster Hardware — You might think your workstation's CPU is pretty fast, but imagine having an AMD EPYC with 192 cores per socket and 10 terabytes of RAM! Modern CPU power (not to mention much faster storage) invites us to ask questions about modern ways to scale database servers.

Lætitia Avrot