Sammlung von Newsfeeds

Introduction

PGDay Boston 2026 was a rewarding reminder of why I value the PostgreSQL community so much. It was delightful to reconnect with familiar faces, meet new people, and finally put some faces to names for the first time. One of the best parts of the day was the sense that this community is larger than any one employer or project. It is built on shared curiosity, shared responsibility, and a willingness to help one another learn. I’m honored to have been able to share my own thoughts in my Disaster Recovery talk as well.

Introduction

PGDay Boston 2026 was a rewarding reminder of why I value the PostgreSQL community so much. It was delightful to reconnect with familiar faces, meet new people, and finally put some faces to names for the first time. One of the best parts of the day was the sense that this community is larger than any one employer or project. It is built on shared curiosity, shared responsibility, and a willingness to help one another learn.

PostgreSQL's `deadlock_timeout` controls how often deadlocks are searched for, not how long a deadlock will be tolerated.

#​652 — June 10, 2026

Web Version

Postgres Weekly

The Prague PosgreSQL User Group met on June 1, 2026, organized by Gülçin Yıldırım Jelínek and Mayur B.

Speaker:

• Laurenz Albe
• Josef Šimánek
• Ants Aasma

PGDay France 2026 took place from June 3-4

Organizers:

The old Postgres Conferences always sounded interesting, but the conference being in Ottawa in Canada and me being in Europe, I've always dismissed them as "too far away" and never bothered going.

Then the organizing team changed and the conference moved to Vancouver for 2024. That's even further away. 2025 in Montreal was a bit closer again, but…

PostgreSQL's DateStyle parameter does two unrelated things at once, which explains why it confuses everyone.

PostgeSQL 19 beta 1 has been released on 2026-06-04.

The release is planned for September 2026, though it’s time to go through the new features and changes.

My Top Three Features

All three features below are cool and great developments from the authors of the patches that implemented them. But there are a lot of new cool features and extesnions to exisiting features done by a lot of people.

Every PostgreSQL developer eventually reaches the same architectural boundary, although the boundary usually appears as an ordinary product request rather than a database design problem. An application transaction needs to complete one business operation, but the surrounding platform also needs to write an audit record, launch a slow report, refresh a cache, fire a notification, or start some enrichment logic that should not delay the user.

PostgreSQL's query planner gathers statistics one way; Oracle, Db2, MySQL, SQLite, DuckDB, and Snowflake each chose differently.

data_sync_retry is a boolean, it defaults to off, and its context is postmaster so changing it needs a restart. You will almost certainly never change it. It exists as the visible scar tissue from the single most unsettling thing the PostgreSQL community ever learned about its own durability assu…