Neues vom PostgreSQL Planet

Earlier this year, I had the incredible opportunity to present at PGConf India, where I delved into the intricacies of Write-Ahead Logging (WAL) in PostgreSQL. My presentation aimed to demystify this crucial database feature that ensures data integrity and enhances performance. 

Why Bridge Java with C in the First Place?

Bridging Java and C combines the strengths of both languages. A C application may rely on Java for modern libraries, cloud APIs, or UI and web capabilities, while a Java app might need C for low-level system access or performance-critical tasks. Sometimes, there’s simply no alternative—certain features only exist in one language. While modern languages like C++ and Go offer both high- and low-level control, many systems aren’t written in them.

With the Postgres 18 Beta 1 release this week a multi-year effort, and significant architectural shift in Postgres is taking shape: Asynchronous I/O (AIO). These capabilities are still under active development, but they represent a fundamental change in how Postgres handles I/O, offering the potential for significant performance gains, particularly in cloud environments where latency is often the bottleneck. Why asynchronous I/O matters How Postgres 17’s read streams paved the way New io_method…

Before we delve into the main subject of this blog, it is essential to understand the benefits of PostgreSQL replication, and the difference between single-master replication (SMR) and multi-master replication (MMR). In every modern business application, the database is becoming a critical part of the architecture and the demand for making the database performant and highly available is growing tremendously.

Howto guide for upgrading PostgreSQL from version 16 to 17 on Ubuntu, after its upgrade from version 24.10 to 25.04 (Plucky Puffin).

In the PostgreSQL world, as well as in order database systems, data types play a crucial role in ensuring optimal performance, efficiency, as well as semantics. Moreover, some data types are inherently easier and faster to index than others. Many people are not aware of the fact that indexes indeed make a difference, so let us take a look and see how long it takes to index the very same data using different
types.

The last Extension Ecosystem Mini-Summit is upon us. How did that happen?

PostgreSQL 18 changes this week

The PostgreSQL release is slowly taking shape, with the first draft of release notes now available. Corrections and additions can be sent via the pgsql-hackers thread " PG 18 release notes draft committed ".

You know I had to do it as soon as I found it was possible. Yes, I installed and enabled AI in the DBeaver Query Editor so I can use AI with my PostgreSQL database work. Let’s face it. It was inevitable. However, the setup isn’t intuitive. Setting Up in DBeaver I’m going to assume […]

The post AI in the DBeaver Query Editor appeared first on Grant Fritchey.

On 8th of April 2025, Daniel Gustafsson committed patch: Add function to get memory context stats for processes   This adds a function for retrieving memory context statistics and information from backends as well as auxiliary processes. The intended usecase is cluster debugging when under memory pressure or unanticipated memory usage characteristics.

This blog posting is part of a series about organizing Meetups. While mostly centered around PostgreSQL Meetups, large parts can be adapted by other Meetups as well. All postings in this series: Checklist for Meetup Attendees (this posting) Checklist for Meetup Speakers Checklist for Meetup Organizers Overview posting Attending an in-person Meetup You found an interesting Meetup, and like to sign up. Before you sign up, please read the entire Meetup description.

This blog posting is part of a series about organizing Meetups. While mostly centered around PostgreSQL Meetups, large parts can be adapted by other Meetups as well. All postings in this series: Checklist for Meetup Attendees Checklist for Meetup Speakers Checklist for Meetup Organizers (this posting) Overview posting You are organizing a Meetup. Congratulations, this is big! Here are some recommendations: First things first: find a date. Pay attention to school holidays and public holidays, especially for in-person Meetups.

This blog posting is part of a series about organizing Meetups. While mostly centered around PostgreSQL Meetups, large parts can be adapted by other Meetups as well. All postings in this series: Checklist for Meetup Attendees Checklist for Meetup Speakers (this posting) Checklist for Meetup Organizers Overview posting You are speaking at a Meetup. Congratulations! General advice Check your slides for a good contrast, and fonts large enough.

A few days ago, I wrote about a surprising planner behavior with CTEs, DELETE, and LIMIT in PostgreSQL, a piece I hastily put together on a bus ride. That post clearly only scratched the surface of a deeper issue that I’ve since spent way too many hours exploring. So here are some more formed thoughts and findings. The core issue revisited Let’s quickly recap: when using a query like the following, the planner might execute your query in ways you don’t expect.

Greetings!

Fault tolerance is a very important aspect of every non-startup application.
It can be described as a definition:

Fault tolerance is the ability of a system to maintain proper operation despite failures or faults in one or more of its components.

But this gives only slight overview - fault tolerance concerns many areas especially when we are talking about software engineering:

I have just completed the first draft of the Postgres 18 release notes. It includes a little developer community feedback but still needs more XML markup and links.

Slides and transcript from my talk, "Anatomy of a Database Operation", at DjangoCon Europe in Dublin on 25 April 2025.

I'll share the recording as soon as it's available.

On April 23, we hosted the fourth of five (5) virtual Mini-Summits that lead up to the big one at the Postgres Development Conference (PGConf.dev), taking place May 13-16, in Montreál, Canada.

On 7th of April 2025, Álvaro Herrera committed patch: Allow NOT NULL constraints to be added as NOT VALID   This allows them to be added without scanning the table, and validating them afterwards without holding access exclusive lock on the table after any violating rows have been deleted or fixed.   Doing ALTER TABLE … Continue reading "Waiting for PostgreSQL 18 – Allow NOT NULL constraints to be added as NOT VALID"

 I am (slowly) adding handy PostgreSQL queries to my GitHub, and Vacuum is the newest category.  The end goal is to have a compilation of queries for those of us who need to keep an instance healthy.

Over the years, I have collected hundreds of various queries and hate hunting them down in my code snippet library. Finally, they will be in one place and easy to search. 

Please contribute if you have similar or better queries (hint, hint!).