Neues vom PostgreSQL Planet

Clearly it's summer time in the Northern Hemisphere and we haven't been as punctual with our recognition posts! We'll resume to a more regular schedule, promised!

On Aug, 28 Peter Zaitsev and Emma Saroyan organised PG Armenia x Percona University.

Speakers: * Peter Zaitsev * Andrey Borodin * Emma Saroyan * Konstantin Trushin * Dmitrii Kochetov * Alexey Palazhchenko * Alex Demidoff * Eugene Klimov * Kim Saroyan * Alexander Zaitsev * Aya Guseinova * Piotr Kalmukhyan

Yesterday someone posted a set of queries for interviews, all centered on answering business-like questions from database. Today this post is hidden behind some “subscribe to read more" thing, so I will not even link it, but one question there caught my eye. Since I can't copy paste the text, I'll try to write what … Continue reading "Who logged to system from multiple countries in 2 hours?"

The PostgreSQL development group released the second Beta version of PostgreSQL 18 in July; the GA version is expected later in 2025 (around the September/October timeframe). The PostgreSQL development group and its community is very dedicated and ensures several minor releases during the year and major releases every year.

Row-level security (RLS) is a great feature. It allows restricting access to rows by applying filters defined by a policy. It’s a tool useful for cases when the data set can’t be split into separate databases.

PostgreSQL 19 changes this week ALTER DOMAIN ALTER DOMAIN ... VALIDATE CONSTRAINT executes at lock level ShareUpdateExclusivelock instead of ShareLock PL/Python event trigger support added sync_replication_slots if enabled, now requires wal_level to be set to logical

more...

The PostGIS Team is pleased to release PostGIS 3.6.0rc2! Best Served with PostgreSQL 18 Beta3 and recently released GEOS 3.14.0.

This version requires PostgreSQL 12 - 18beta3, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take advantage of all SFCGAL features, SFCGAL 2.2.0+ is needed.

The middle of August tends to be a quieter time in the PostgreSQL development cycle, so there's not much in the way of new developmentst to report.

This week's main item of interest is the quarterly release of PostgreSQL minor version updates.

PostgreSQL 19 changes this week

PostgreSQL 19 beta3 was released this week.

more...

When working with customers, a common question we get is: “Which standby type is best for our HA needs?” Before answering, we ensure they fully understand the concepts behind each standby type and provide the necessary guidance

A standby server is essentially a copy of your primary database that can take over if the primary fails.

There are different types of standby setups, each with its own use cases, pros, and cons. In this blog, we will discuss the three types: Cold Standby, Warm Standby, and Hot Standby.

PostgreSQL 19 changes this week pg_stat_progress_basebackup column backup_type added PostgreSQL 18 articles "enable" parameters will work differently in Postgres 18 (2025-08-07) - Michael Christofides / pgMustard

more...

This is the second part of the series I started on Learning PostgreSQL from AI and JSON exploration: Part 1. For this 2nd part, I decided to try gpt-oss the 14GB model which was just released in the past week. My first impression, "When will this ai shut up about its thinking process?".

Introduction

In our CNPG series, we have explained how to create a PostgreSQL cluster and how to customize it. However, most of the time, we don't have the luxury to start to use a database from scratch. We might have already started a project without high availability and we might be looking for an easy-to-manage environment on cloud native environment. In this case, CNPG is the answer, but how do we migrate our existing cluster to CNPG? In today's article, we will explain that.

SLAs feel reassuring when signed—but their substance lies in what happens behind the scenes. Often, the most damaging breaches don’t stem from cloud outages or server failures, but from invisible issues hidden in how PostgreSQL was initially set up and configured. Increasingly sluggish queries, split-brain scenarios, silent backup failures, any of these can suddenly explode into customer-facing crises.

When I started working with Postgres (or databases in general) 25 years ago, storage systems looked very different. All storage was “spinning rust” - rotational disks with various interfaces (SATA/SAS/…) and speeds (7.2K/10k/15k/…). The spindle speed was the main performance determining feature, and everyone knew what IOPS and bandwidth to expect from a disk. The general behavior was pretty much the same.

Table of Contents

• Indexes
• Users and Connections
• Splitting Data over Disks
• Network
• Vacuum

A modern-day Postgres instance creates robust and comprehensive logs for nearly every facet of database and query behavior. While Postgres logs are the go-to place for finding and debugging critical errors, they are also a key tool in application performance monitoring.

When many sessions try to insert into the same B-tree leaf page, classic exclusive page locking serializes progress and wastes time on sleep/wake cycles. We’re introducing a batch page insertion path that lets the session holding the page lock insert for itself and its neighbors. The result: dramatically reduced lock waits, and big gains at high client counts (2X throughput boost starting from 64 clients in our benchmark).

pgsql_tweaks is a bundle of functions and views for PostgreSQL

One could install the whole package, or just copy what is needed from the source code.

The extension is also available on PGXN.

The extension is also availabe through the PostgreSQL rpm packages.

General changes

No code has been changed.

PostgreSQL 19 changes this week pg_stat_statements counters for generic and custom plans added EXPLAIN memoize planner estimates now displayed logging misleading hint about buggy kernels for "unexpected data beyond EOF" error removed PostgreSQL 18 changes this week pg_dumpall support for non-text modes added to (and corresponding support in pg_restore ) has been reverted due to concerns about robustness and security; it is hoped this feature can be re-added in PostgreSQL 19.

The PostGIS Team is pleased to release PostGIS 3.6.0rc1! Best Served with PostgreSQL 18 Beta3 and soon to be released GEOS 3.14.

This version requires PostgreSQL 12 - 18beta3, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take advantage of all SFCGAL features, SFCGAL 2.2.0+ is needed.

pgsql_tweaks is a bundle of functions and views for PostgreSQL

One could install the whole package, or just copy what is needed from the source code.

The extension is also available on PGXN.

The extension is also availabe through the PostgreSQL rpm packages.