Neues vom PostgreSQL Planet

In this article, I explore how CloudNativePG 1.27 enhances PostgreSQL liveness probes, including primary isolation checks that mitigate split-brain scenarios and integrate seamlessly with Kubernetes. We also discuss how these improvements lay the groundwork for advanced features like quorum-based failover while maintaining stability, safety, and community-driven decision-making.

PostgreSQL Hacker Helper is a VS Code extension for developing PostgreSQL source code. A couple of days ago (August 9th), one year has passed since the release of version 1.0.0.

Initially, it was a utility for dynamically calculating expressions and casting variables, but after a while I realized that not everything is so simple. The main catch is that there are types (if you can say so) that require special treatment.

A short summary of Free PostgreSQL® services in the cloud as of August 14th 2025

At Percona, we believe that great open source software is built with the Community, not just for it. As we plan the next iteration of pg_stat_monitor, our advanced PostgreSQL monitoring extension, we’re taking a closer look at the current feature set and how it aligns with real-world usage. In open source, the community isn’t just a user base, it’s the most important stakeholder. While we set the vision, your feedback is the compass that guides us.

© Laurenz Albe 2025

PostgreSQL links Blogs, podcasts, newsletters etc. Scaling Postgres 376: 100K Events Per Second Queue (2025-07-27) Postgres Weekly Issue 609 (2 025-07-27) Contributions for the week of 2025-07-14 (Week 29) ( 2025-07-22) Announcements PGDay Napoli 2025, Schedule and Registration  (2025-07-22) Autobase 2.3.0 released  (2025-07-21) Autobase is an open-source, self-hosted DBaaS platform for PostgreSQL Others PostgreSQL Person of the Week:Peter Zaitsev (2025-07-21)

more...

I’ve used PostgreSQL for almost 20 years. During this time, I’ve struggled with its official clients. Normally, I have a good memory (except for people’s names and faces). So having to refer to the tool documentation each time I wanted to use it was very unusual for me. So I asked myself, why is that so? I noticed that there was inconsistency and even incompatibility among flags. Sometimes you need the -d flag for the database name.

Table of Contents

• PostgreSQL Extensions
• Available In Clouds
• Manged by Me, or Contributed to by Me
• The Ones You Always Will Need

Postgres is amazing for many reasons. One area that doesn't get near enough attention is datatypes. Postgres has a rich set of datatypes and one important one for devs to be especially excited about is JSONB.

JSONB which is structured and indexable. In JSON, the B stands for binary (or as we like to think of it B is for better), which means data is pre-parsed as it is stored. How do you get the most out of JSONB from a retrieval perspective? Enter Postgres' rich indexing support.

PostgreSQL Person of the Week Interview with Curt Kolovson: I grew up in the Boston area. I currently live in the San Francisco Bay Area and have resided here for over 40 years.

PostgreSQL and GB18030-2022 Support

PostgreSQL supports GB18030 as a client-side encoding. A client-side encoding means you can set the encoding from a client application such as psql with:

psql=# set client_encoding to GB18030

This tells the PostgreSQL backend that the client will send SQL statements encoded in GB18030. When the backend receives a statement, it converts the GB18030 byte stream into UTF-8 (the default server-side encoding), and then passes it to exec_simple_query() for execution.

I subscribe to Medium (don’t judge), and their weekly summary pushed an article to me entitled The Postgres Revolution Is Here: Why Version 18 Changes Everything for Developers. Well, OK, that sounds relevant to my interests. Let’s check it out!

Oh.

Oh, dear.

Oh, sweet Mother of God.

PostgreSQL’s hash partitioning distributes rows across partitions using deterministic hash functions. When you query through the parent table, PostgreSQL must perform catalog lookups to route each query to the correct partition. This results in measurable overhead for high-throughput applications, especially if you decide to use multi-level partitioning schemes where PostgreSQL must traverse deeper catalog structures to identify the target partition. Let’s take a look at some findings on speeding up the part where you already know the partition key values.

PostgreSQL is having more than just a moment—it’s establishing a clear pattern of sustained excellence. For the third consecutive year, this community-driven database has claimed the top spot in the 2025 results for Stack Overflow’s Annual Developer Survey, and the results reveal both what developers value today and where the database landscape is heading.

When you are running mission-critical applications, like online banking, healthcare systems, or global e-commerce platforms, every second of downtime can cost millions and damage your business reputation. That’s why many customers aim for four-nines (99.99%) or five-nines (99.999%) availability for their applications

In this post, we will walk through what those nines really mean and, more importantly, which PostgreSQL cluster setup will get you there.

A comparison of logical replication and ETL for syncing data with Postgres

What do tech journalism, PR, and PostgreSQL have in common? For Elly Phneah, the answer is community. Based in Malmö, Elly is the driving force behind the Malmö Postgres User Group (M‑PUG, for short), where she combines her background in communications with a deep passion for databases and developer communities.

GSoC 2025 Project Report, PostgreSQL Upgrade pgwatch Grafana dashboards to v12

Contributor: Gaurav Patidar

Organisation: PostgreSQL

Mentors: Pavlo Golub, Rajiv Harlalka

Project Repository: pgwatch_grafana

Photo by Elnaz Asadi

Each year I go through the changes and additions to EXPLAIN in the upcoming PostgreSQL major version, to see what we need to add support for in pgMustard.

In the previous post, I explored some nuances of Postgres related to indexes and parallel workers. This text sparked a lively discussion on LinkedIn, during which one commentator (thanks to Ants Aasma) proposed an index that was significantly more efficient than those discussed in the article.