Plus a deadlock bug in Postgres 14-16, C64 BASIC in Postgres, and a fresh round of events.

#​656 — July 8, 2026

Web Version

Together with  ParadeDB

Postgres Weekly

Postgres is Enough: How Postgres Can Replace Other Things — A perennial topic in the Postgres world is figuring out just how many other systems (like Redis, Elasticsearch and Kafka, say) Postgres can step in for. This directory rounds up 89 extensions and tools that help Postgres do just that.

Goodway

Search Without a Second System — One Postgres for your application data, full-text search, vector retrieval, and aggregations. ParadeDB is an open-source Postgres extension that keeps pace with Elasticsearch.

ParadeDB sponsor

Postgres Transactions are a Distributed Systems Superpower — Should workflow state live in a separate orchestrator, or in Postgres alongside your data? DBOS argues the latter: each step's checkpoint and database updates commit in one transaction, giving exactly-once semantics for those updates with no idempotency bookkeeping.

Kraft and Li (DBOS)

💡 DBOSify puts the idea above into practice as a drop-in replacement for Temporal's Python SDK that uses Postgres with no Temporal server needed.

Why PgDog Built Yet Another Postgres Connection Pooler — Reducing user tradeoffs and providing a seamless experience, largely. For example, unlike PgBouncer, it keeps SET and LISTEN/NOTIFY working in transaction mode.

Lev Kokotov

🚨 A Replication Deadlock Bug in Current Postgres 14-16 Releases — A report that v14.23, v15.18, and v16.14 introduced a regression that can lead to a MultiXactOffsetSLRU deadlock during transaction log replay in some circumstances.

Credativ

Waiting for Postgres 20: Add Backend-Level Lock Statistics — Postgres 19 isn't here yet, but Hubert's looking forward to v20 and its forthcoming per-backend lock statistics, which will show which connections are stuck waiting on locks, and for how long.

Hubert 'depesz' Lubaczewski

📄 Understanding Postgres 19 Property Graphs – A deeper look at mapping relational schemas onto property graphs, gotchas included. Rimas Silkaitis

📄 Looking Forward to Postgres 19: Split PersonalityALTER TABLE is gaining SPLIT PARTITION and MERGE PARTITIONS options. Shaun Thomas

📄 Using Postgres as a Temporal Database Gulcin Yildirim Jelinek (Xata)

📄 Some More Thoughts on random_page_cost Tomas Vondra

RELEASES AND CODE:

pREST 2.0: Serve a RESTful API From a Postgres Database — Turn a Postgres database into a RESTful API. Covers similar ground to PostgREST but built in Go rather than Haskell. v2.0 adds support for multiple databases.

pREST Team

PL/Ruby 2.5: Ruby as a Procedural Language for Postgres — Lets you write functions, triggers, event triggers, and procedures for Postgres in Ruby.

Joshua D. Drake (Command Prompt Inc.)

PL/CBMBASIC: Commodore 64 BASIC for Postgres — I like to slip a fun item in every now and then, and it doesn't get more fun than writing Postgres functions in a 44-year-old programming language.. does it? 😅

Thom Brown

Tinbase: A Supabase-Compatible Backend in a Single Binary — An experiment that provides a local Supabase-like dev experience without Docker using a pure-JS backend built on PGlite and pg-mem. A sort of mini, local-only Postgres wrapped in the same APIs as Supabase proper, so supabase-js works unchanged.

Sanket Sahu

pglayers: Postgres Extensions as Docker Layers — The official Postgres Docker images ship with few extensions and adding more can become tricky. pglayers tries to make this easier by layering extensions atop the official image.

Ismaël Mejía

  • pgcopydb 0.18 – Copy a Postgres database to a target server (a turbocharged pg_dump | pg_restore, if you will).

  • PostGIS 3.7.0 Alpha 1ST_DWithin gets a major speed boost, Postgres 12/13 support is dropped, address_standardizer and tiger_geocoder are spun out into their own repos.

  • River 0.40 – Job processing system for Go using Postgres. Contains a schema cleanup migration and adds JobStuckHandler as a hook for handling stuck jobs.

📰 Classifieds

📊 OSS observability for any Postgres 14+. Tiered anomaly detection, historical metrics. Natural-language chat optional.


No more sales calls for Postgres. Pick your product, check out, and scale on your own terms. No waiting on a quote.

Note: This list is not exhaustive, and we will continue to mention and promote other events over time.