Sammlung von Newsfeeds

Boring is an investment. Exciting is a bill.

The calmest PostgreSQL deployments in production share one trait. They are boring. Pages stay quiet. Dashboards stay green. The on-call engineer reads a book on Tuesday night. And the people running those databases will tell you, plainly, that boring is the achievement.

If you are using PostgreSQL in any capacity very likely this week has started for you with a bang. pgBackRest, one of the most known tools for PostgreSQL, praised for the scalable and reliable way to do backups has announced that the project is currently archived.

If you are using PostgreSQL in any capacity very likely this week has started for you with a bang. pgBackRest, one of the most known tools for PostgreSQL, praised for the scalable and reliable way to do backups has announced that the project is currently archived.

Part 3 of the Semantic Caching in PostgreSQL series. Part 1 covers the fundamentals of  — how it stores query embeddings, runs cosine similarity searches via pgvector, and returns cached LLM results without a round-trip to your model provider.

I flew 12 hours to Pasadena, survived the sunshine, and came back with a vlog (or pavlog? 🙂) Worth it? Absolutely.

SCALE 23x is one of those events where the hallway conversations are as valuable as the talks. I grabbed my camera and tried to capture some of that energy. Featuring Bruce Momjian, Elizabeth Christensen, Mark Wong, and Gabrielle Roth — people who have been building this community for years.

This blog is based on a real production case in which users experienced a serious delay in logical replication. Let me try to explain how to approach similar cases and analyze them in an easy method, because lag in logical replication is a common problem, and we should expect it to come up for different environments. But sometimes troubleshooting can be challenging, especially on DBaaS environments where we won’t get in-depth information at OS / hardware level.

We leave the archive arc behind and enter the first of several backward-compatibility GUCs. array_nulls controls whether the array input parser treats an unquoted NULL as an actual SQL null or as the four-character string "NULL". Default is on; context is user; it has been on by default since Pos…

An interesting article about PostgreSQL and Open Source.

A very illuminating article about contributing to Open Source and PostgreSQL

Abdelrhman Sersawy wrote an article titled How I started contributing to PostgreSQL in which he describes how he started to write code for the community.

A new release of the fast connection pooler for PostgreSQL!

pgagroal 2.1.0 is out!

Yesterday the version 2.1.0 of pgagroal has been released! This is a feature release, and the full changelog is available here.

This release provides a lot of new features, most notably:

PostgreSQL 18 shipped asynchronous I/O. PostgreSQL 19, currently in feature freeze and headed for a September release, makes it tolerable to operate. That sounds like a snide reading. It is not. The AIO subsystem in PG18 was a serious piece of engineering, and on the workloads it covers — sequent…

Time zones are an unfortunately complex subject when dealing with PostgreSQL. You may be running your local time zone on your on-premises server or on your own laptop. Or you may be using the time zone of your server’s physical location. And you may have set all your servers to UTC. And all are valid approaches, depending on your circumstances.

DBeaver users know it is a very advanced tool for database work. But it is easy to get into time zone issues, as the default time zone for your session is taken from your client machine. But this can be adjusted.

For about fifteen years, the standard answer to “this table is bloated, what do I actually do about it” has been one of the out-of-tree options: pg_repack (the extension), pg_squeeze (Antonin Houska’s predecessor work), or a hand-rolled CREATE TABLE AS and swap. PG19 changes tha…

Another great evening for the PostgresEDI community! 🐘

First off, a massive thank you to everyone who came out to our April meetup. The discussions were brilliant, and it's amazing to see new faces come to experience the friendly environment at our meetups.

The archiver only runs when a WAL segment is complete. On a busy database that happens constantly; on a quiet one it might not happen for hours or days. archive_timeout exists to prevent the resulting “our database has been accepting writes all afternoon but none of them are in the archive …

Hello everyone, here comes a series of my annual posts about the Chicago Postgres Conference, and what I am most excited about. And I want to start with the training sessions we offer. All three training sessions are presented by my favorite people, and I can’t wait to tell you more about them!

#​646 — April 29, 2026

Web Version

Postgres Weekly

PgBackRest Is Dead

Yesterday the maintainer of PgBackRest, David Steele, published the NOTICE OF OBSOLESCENCE.

For further information please read the blog post pgBackRest is dead. Now what? by Lætitia Avrot. She also points to how to go an as she, like me, always recommended PgBackRest for PostgreSQL backups.

First in a series of dispassionate surveys of the major managed-Postgres offerings. This post is about Amazon RDS for PostgreSQL — what AWS calls “traditional RDS,” as distinct from Aurora PostgreSQL, which is a separate product with a separate architecture and will get its own post. …

In the previous article we watched every UPDATE leave dead tuple behind. The same copy-on-write behaviour shows up from the operational angle in DELETEs are difficult. That's the tradeoff of MVCC and on the heap alone it's tolerable. The problem is the indexes.

PostgreSQL 19 ships with parallel autovacuum. The new GUC autovacuum_max_parallel_workers caps the cluster-wide pool, and the per-table storage parameter autovacuum_parallel_workers lets you tune individual tables. Workers come out of the existing max_parallel_workers budget. Off by default. Good…