Sammlung von Newsfeeds
Antony Pegg: How to Build a RAG Server on pgEdge Cloud via the API
This blog is going to show you how to set up your own RAG Server on pgEdge Cloud. The Cloud UI makes this so easy it is almost insulting - a few clicks and you are done - so I am going to show you the harder and more interesting path instead: the Cloud API. Everything below is a real call you can adapt. Replace anything in with your own values, and keep your API keys out of your shell history.Click on "Services" under your database, click on "Add RAG Server" and enter your config. see? sooo easy. Soooo boring.
Thom Brown: LOAD "PL/CBMBASIC",8,1: Commodore 64 BASIC for PostgreSQL
If you are of a certain age, the words 38911 BASIC BYTES FREE will do something to you that no amount of therapy can undo. You remember the blue screen. You remember typing in three pages of a listing from a magazine, getting ?SYNTAX ERROR IN 2340, and not knowing which of the three pages contained the typo. You remember that the disk drive was device 8, and that it was slower than continental drift.
I have some news. All of that now runs inside PostgreSQL.
Henrietta Dombrovskaya: Estonia PUG Meetup
Yesterday, I had the pleasure of presenting at the Postgres User Group Estonia, and that was a delightful experience! Many thanks to Ervin Weber, who literally spent three years trying to make it happen. I was happy to give back to one of my favorite places in the world – the city of Tallinn.
Christophe Pettus: All Your GUCs in a Row: enable_nestloop
Hans-Juergen Schoenig: Following a Backup from PostgreSQL to Recovery using pg_hardstorage
For PostgreSQL administrators, DBAs, SREs, and platform teams, understanding how backup data moves through a system is just as important as knowing when a backup completed successfully. Questions about repository layout, WAL handling, metadata, integrity, and recovery usually surface when troubleshooting, validating a backup strategy, or preparing for recovery.
Christophe Pettus: All Your GUCs in a Row: enable_mergejoin
Zhang Chen: Extreme Rescue: PostgreSQL Full-File Ransomware Recovery at Epic Difficulty
Ahsan Hadi: Introducing pg-healthcheck: PostgreSQL Health Diagnostics
After more than 20 years working with PostgreSQL, I keep seeing the same problems surface at the worst possible times - bloat that sneaks up on you, replication slots quietly holding back WAL, transaction ID wraparound that nobody caught in time, backups that silently stopped working weeks ago. There are also data and catalog corruption issues like TOAST table corruption or a mismatch between heap state and VM state causing problems with vacuum operations. What I always wanted was a single tool I could point at any PostgreSQL instance and get a clear, actionable picture of its health.
Dimitri Fontaine: pgcopydb v0.18
Hot off the press: pgcopydb v0.18 is out!
It’s the biggest release the project has had — 88 commits since v0.17, which shipped in August 2024. I took a break from my Open Source responsibilities for a while, because I was lacking employer support to make it happen.
warda bibi: Inside a PostgreSQL Checkpointer Bug: A Production Postmortem
One of our client’s PostgreSQL 16.8 production databases started logging what looked like a memory error:
ERROR: invalid memory alloc request sizeThe error immediately pointed toward two likely suspects:
Christophe Pettus: All Your GUCs in a Row: enable_material and enable_memoize
Zhang Chen: The PostgreSQL Feature That Makes Data Recovery Painful
Stefanie Janine Stölting: pgsql_tweaks Version 1.0.5 Released
Postgres in Production Special Series: Configuring pg_stat_statements to Reduce Deallocations (Part 5)
In Part 5 of this special Postgres in Production deep dive series, Ryan Booz turns to configuration. There are only a handful of settings that control how pg_stat_statements behaves, but they decide how much data you keep and how much you lose. This episode covers how to see when you’re losing data through deallocations, what each setting actually does, and the changes (in settings and in your application) that reduce data loss over time.
Laurenz Albe: Too many tables are bad for you
© Laurenz Albe 2026 (see here for more background)
Recently, I helped a customer investigate database problems. It turned out that these problems could be traced back to too many tables in the database. Since this may come as a surprise to many users, I thought it worth the while to write about it.
The problems that the customer observedThere were two problems that sounded like they might or might not be related to each other:
Peter Eisentraut: Waiting for SQL:202y: Stockholm (BMA) meeting report
The most recent meeting of ISO/IEC JTC1 SC32 WG3 “Database Languages” took place from the 15th to the 19th of June 2026 in Stockholm. “WG3”, as we call it, works on standardizing the database languages SQL and GQL. In that meeting, a number of proposals that are of interest to SQL and PostgreSQL were accepted, which I want to report about here.
