PgQue shipped its v0.1 last week, and the part I want to talk about is not what the announcement leads with — managed-Postgres compatibility, no C extension, no daemon. Those are real, but they’re packaging. The part that’s worth understanding is the implementation, because PgQue is a working in-database queue whose hot path contains zero UPDATEs, zero DELETEs,

This parameter is the last line of defense against PostgreSQL’s most famous failure mode. To explain what it does, a brief detour into how PostgreSQL knows which rows you are allowed to see.

These two are inseparable. They combine in a single formula that decides when autovacuum runs ANALYZE against a table, and discussing one without the other gives you half a picture. So: a double-header.

The formula:

1
analyze threshold = autovacuum_analyze_threshold
2
                  + autovacuum_analyze_scale_factor × reltuples

When the number of tuples inserted, updated, or deleted since

If you have ever run pg_ctl stop -m fast on a primary and watched it hang well past wal_sender_shutdown_timeout, you have met a bug that has been sitting in walsender.c for years. As of commit c0b24b3 on master (Fujii Masao, May 1, reported by Andres Freund via FreeBSD CI), it is fixed. PostgreSQL 19 will enforce the timeout. PostgreSQL

autovacuum is a boolean. Default on, context sighup. Set it to off for any meaningful length of time and you have purchased a tour of every PostgreSQL failure mode worth knowing about, in escalating order, at no extra charge. Let me describe the tour.

The autovacuum launcher and its workers run VACUUM and ANALYZE against tables based

Bruce Momjian posted the first draft of the PostgreSQL 19 release notes to pgsql-hackers on April 15. The count, by his own enumeration, is 212 items. Feature freeze landed a week earlier on April 8. Beta 1 is expected next month. The final release is on the calendar for September.

Two hundred and twelve is a lot of items,

PGX is providing continuity support for pgBackRest, under the name pgxbackup.

pgBackRest has been the gold standard for PostgreSQL backup and restore for over a decade. David Steele built it, maintained it, and shaped how a generation of PostgreSQL DBAs think about backup. It earned its place in production because it does the unglamorous things correctly: parallel backup

A connection is not free just because it has not logged in yet. From the moment the TCP handshake completes, the would-be client is holding a backend slot counted against max_connections, and it will hold that slot until one of two things happens: it finishes the authentication protocol, or authentication_timeout kicks in and the server hangs up on it.

pgvector is excellent. It is also, at large scale, expensive — because the HNSW index it gives you wants to live in memory to be fast, and “wants to live in memory” stops being a casual statement somewhere around fifty million 1536-dimensional embeddings. At which point you reach for Pinecone, or you scale up the box, or you wave your

The php.internals vote closed on April 4, and PHP 9.0 will ship under the 3-clause BSD license. The RFC, driven by Ben Ramsey, replaces both the PHP License v3.01 and the Zend Engine License v2.0 with a single, OSI-recognized, FSF-recognized, GPL-compatible permissive license that has been sitting on the shelf for thirty-five years. This is a good decision, and the