Sammlung von Newsfeeds

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.

PostgreSQL is built to perform. However, as workloads increase and systems evolve, even the most robust setups can begin to show signs of strain. Whether you are scaling a product or supporting enterprise SLAs, performance slowdowns tend to surface when you least want them to.

If you are a technology leader overseeing a team of developers who manage PostgreSQL as part of a broader application stack, or you are responsible for uptime and customer satisfaction at scale, knowing where to look first can make all the difference.

Introduction

The importance of backups is universally acknowledged in our digital world. One of my former esteemed colleagues told me that he can't think of a database system without backups. This perspective has resonated with me over the years. Today, in our CNPG series, we will be taking a look at the backup solution and how we restore a database from the backup.

     Authors find it challenging to write a comprehensive book about PostgreSQL for several reasons. The first is that a new version of PostgreSQL is released every year with changes, new features, and tweaks.  I am lucky to have been able to review several new database titles each year, and I would like to let you know that Hans-Jurgen Schonig's Mastering PostgreSQL is a well-written reference. 

PostgreSQL has a fairly efficient buffer manager that handles data movement between shared memory and disk storage. Among other things, its primary purpose is to serve as a disk cache for the client backend processes for quick access to data. The size of this buffer is dictated by the setting shared_buffers in postgresql.conf, and its default value is 128 MB.

Broadcasting a quick tip from a real-life “tasklet” where a customer was genuinely surprised why a seemingly logical fix didn’t show up on Google / LLM-s. So let’s see if we can improve on that situation. So in short a large central table was getting too bloated (fragmented) and query...

PostgreSQL 18 is on the way, bringing a set of improvements that many organizations will find useful. It’s not a revolutionary release, but it does move things in a good direction, especially in performance, replication, and simplifying daily operations. For teams already using PostgreSQL, it’s a good time to look into what’s new. For others […]

PostgreSQL Person of the Week Interview with Shlok Kumar Kyal: My name is Shlok Kumar Kyal. I live in Bangalore, India. I am currently part of the PostgreSQL Open Source team at Fujitsu.

I often hear that PostgreSQL is not suitable for solving analytics problems, referencing TPC-H or ClickBench results as evidence. Surely, handling a straightforward task like sorting through 100 million rows on disk and calculating a set of aggregates, you would get stuck on the storage format and parallelisation issues that limit the ability to optimise the DBMS.

On 29th of July 2025, David Rowley committed patch: Display Memoize planner estimates in EXPLAIN   There've been a few complaints that it can be overly difficult to figure out why the planner picked a Memoize plan. To help address that, here we adjust the EXPLAIN output to display the following additional details:   1) … Continue reading "Waiting for PostgreSQL 19 – Display Memoize planner estimates in EXPLAIN"

Just a short post, because I thought this was pretty remarkable. Below, I have screenshots showing the CPU utilization of two AWS instances in us-west-2 which are running an identical workload.