Sammlung von Newsfeeds

Introduction

In our CNPG series, we have mentioned that backups are crucial in every database system in case of any disaster. PostgreSQL has powerful recovery capabilities as well as backup capabilities, including the ability to restore a database cluster to a specific moment in time. This is extremely useful in scenarios where we need to recover from user errors—such as accidental data deletion, wrong updates, dropped tables, or even dropped databases.

Daria Aleshkova, Oleksii Kliukin, Sergey Dudoladov and Andreas Scherbaum organized the PostgreSQL Berlin September Meetup. Divyendu Singh and Marko Coha presented talks.

Postgres 18 was released today. Well down page from headline features like async I/O and UUIDv7 support, we get this nice little improvement:

This release adds the capability to access both the previous (OLD) and current (NEW) values in the RETURNING clause for INSERT, UPDATE, DELETE and MERGE commands.

It's not a showstopper the way async I/O is, but it is one of those small features that's invaluable in the right situation.

I recently attended PGDay Lowlands 2025, an awesome PostgreSQL Community Event which took place on September 12th in the wondrous environment of the Rotterdam Zoo. It was a fantastic and focused day of PostgreSQL content, made all the more memorable by being in the company of amazing fish, sea turtles, and penguins!

In this post we’ll cover two types of Postgres internals.

The first internal item is an “SLRU.” The acronym stands for “simple least recently used.” The LRU portion refers to caches and how they work, and SLRUs in Postgres are a collection of these caches.

PostgreSQL 18 offers a couple of new features such as asynchronous I/O (aio), improvements around indexing, and a lot more. However, there is one feature that has really caught my attention. While it might go unnoticed by many users, it is really powerful and, to me, somehow represents everything I like about PostgreSQL.

The improvement I want to focus on today is related to the way the "RETURNING-clause" works in PostgreSQL 18.

September 25th marks the release of PostgreSQL 18. This article covers the March CommitFest and concludes the series covering the new features of the upcoming update. This article turned out quite large, as the last March CommitFest is traditionally the biggest and richest in new features.

PostgreSQL 18 was stamped earlier this week, and as usual there’s a lot of improvements. One of the big architectural changes is asynchronous I/O (AIO), allowing asynchronous scheduling of I/O, giving the database more control and better utilizing the storage.

Logical replication in PostgreSQL has steadily evolved since its introduction in version 10. In a previous blog post, I discussed how PostgreSQL 14 introduced streaming of large transactions. PostgreSQL 16 took this further by enabling parallel apply of large transactions via a non-default subscription option. Now, with PostgreSQL 18, parallel apply is the default behavior—marking a significant milestone in replication performance and scalability.

PostgreSQL 19 changes this week random(min, max) : date and timestamp variants added log_lock_waits now set to on by default ERRCODE_DATA_CORRUPTED error codes will be emitted if VM corruption is discovered during vacuum operations PostgreSQL 18 articles Get Excited About Postgres 18 (2025-09-12) - Elizabeth Garrett Christensen / Crunchy Data 3 Features I am Looking Forward to in PostgreSQL 18 (2025-09-09) - Umair Shahid / Stormatics

more...

After a very long development period, we finally completed the project to rework NOT NULL constraints in PostgreSQL.  This has long been a desire of the Postgres development community, and we finally pulled it off for version 18, which has made me very happy.

I had a chance last week to sit down and read the original academic paper announcing Postgres as a platform and the original design goals from 1986. I was just awestruck at the forethought - and how the original project goals laid the foundation for the database that seems to be taking over the world right now.

The PostgreSQL creators totally nailed it. They laid out a flexible framework for a variety of business use cases that would eventually become the most popular database 30 years later.

Summer is slowly fading, and that means one thing: the PostgreSQL conference season in Europe is officially back. After PGDay Austria on September 4 and PGDay UK on September 9, the next stop was PGDay Lowlands in Rotterdam on September 12. Three conferences in such a short time is a clear sign that the community is back in full swing after the summer break.

If you manage a PostgreSQL database with heavy write activity, one of the most important components to understand is the Write-Ahead Log (WAL). WAL is the foundation of PostgreSQL’s durability and crash recovery as it records every change before it’s applied to the main data files. But because WAL writes are synchronous and frequent, they can also become a serious performance bottleneck when they share the same disk with regular data I/O.

1. pgsql_tweaks is a bundle of functions and views for PostgreSQL

   1. Stefanie Janine Stölting: pgsql_tweaks Version 1.0.2 Released

      Neues vom PostgreSQL Planet - 22. September 2025 - 0:00
      1. pgsql_tweaks is a bundle of functions and views for PostgreSQL

         1. Luca Ferrari: pgenv 1.4.3 is out!

            Neues vom PostgreSQL Planet - 21. September 2025 - 2:00

            A new minor release for the beloved tool to build and manage multiple PostgreSQL instances.

            pgenv 1.4.3 is out!

            pgenv 1.4.3 is out! This minor release fixes a problem in the build of release candidate versions (e.g., 18rc1) by stripping out all the text part from a version number using a Bash regular expression.

      Daniel Vérité: What Unicode versions do we use?

      Neues vom PostgreSQL Planet - 20. September 2025 - 19:40

      With three locale providers (libc, icu and builtin), a PostgreSQL instance has potentially three different versions of Unicode at the same time. In this post, let's see when it matters and how to find which Unicode versions we are using.

      Karen Jex: Postgres Partitioning Best Practices: Sofia's Story

      Neues vom PostgreSQL Planet - 19. September 2025 - 19:04

      Thank you to everyone who came to listen to my talk, "Postgres Partitioning Best Practices", at Euruko in Viana do Castelo, Portugal on 18 September 2025.

      Thank you for all the questions and conversations, and thank you, especially, to the real-life Sofia - the person who found me to say

      "Your talk described exactly what I went through, and I wish I'd been able to watch a talk like this before I started."

      Hans-Juergen Schoenig: PostgreSQL 18: Better I/O performance with AIO

      Neues vom PostgreSQL Planet - 19. September 2025 - 7:00

      PostgreSQL 18 is around the corner and it is time to take a look at one of the most important improvements that have been added to the core engine. We are of course talking about the introduction of asynchronous I/O (AIO), which has been a huge topic over the years. 

      Synchronous vs. asynchronous I/O

      Let's dive into this and understand what the fuzz is all about. The standard I/O model works roughly like this:

      Seiten

      • « erste Seite
      • ‹ vorherige Seite
      • …
      • 4
      • 5
      • 6
      • 7
      • 8
      • 9
      • 10
      • 11
      • 12
      • nächste Seite ›
      • letzte Seite »