#656 — July 8, 2026 |
|
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 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 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 Personality – 📄 Using Postgres as a Temporal Database Gulcin Yildirim Jelinek (Xata) 📄 Some More Thoughts on |
|
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 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 |
|
|
|
|
Got a new email? You can change your address here. Bored of us? Click here to stop getting Postgres Weekly. Got a link for us? Reply and tell us. We can't include everything but we'll look at anything you send. Thanks! Published by Cooper Press Ltd. Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada. |

