Neues vom PostgreSQL Planet
Christopher Winslett: Temporal Joins
My first thought seeing a temporal join in 2008 was, “Why is this query so complex?” The company I was at relied heavily on database queries, as it was a CRM and student success tracking system for colleges and universities. The query returned a filtered list of users and their last associated record from a second table. The hard part about the query isn’t returning the last timestamp or even performing joins, it’s returning only their last associated record from a second table.
Chris Travers: Introduction to NUMA
This series covers the specifics of running PostgreSQL on large systems with many processors. My experience is that people spend months often learning the basics when confronted with the problem. This series tries to dispel these difficulties by providing a clear background into the topics in question. The hope is that future generations of database engineers and administrators don’t have to spend months figuring things out through trial and error.
Valeria Kaplan: PostgreSQL — Blurring the Line Between Mine and Ours
As the biggest PostgreSQL community conference in Europe, PGConf.EU 2025 in Riga, Latvia, kicks off, I feel immense pride in having been part of the small group of people who dedicated their free time to making this event a success.
Dave Stokes: Loading The Titanic Passenger Data Into PostgreSQL With DBeaver Part 2
In the last edition of this blog, the passenger list data from the HMS Titanic was loaded into a preliminary database. Now it is time to refine.
I am using DBeaver Enterprise 25.2.0. PostgreSQL 18, and Github Copilot with Gpt-4.
Prompt: Any recommendations on improving this table for storage efficiency? This prompt was entered into the DBeaver AI Assistant.
Jan Wieremjewicz: Say Hello to OIDC in PostgreSQL 18!
If you’ve ever wondered how to set up OpenID Connect (OIDC) authentication in PostgreSQL, the wait is almost over.
We’ve spent some time exploring what it would take to make OIDC easier and more reliable to use with PostgreSQL. And now, we’re happy to share the first results of that work.
Why OIDC, and why now?We’ve spoken to some of our customers and noticed a trend of moving away from LDAP to OIDC. Our MongoDB product is already providing OIDC integration and the team working on PostgreSQL products saw an opportunity coming with PostgreSQL 18.
Hubert 'depesz' Lubaczewski: Waiting for PostgreSQL 19 – Support COPY TO for partitioned tables.
Chao Li: Understanding the Execution Plan of a Hash Join
A hash join is one of the most common join methods used by PostgreSQL and other relational databases. It works by building a hash table from the smaller input (called the build side) and then probing it with rows from the larger input (the probe side) to find matching join keys.
Hash joins are especially efficient for large, unsorted datasets—particularly when there are no useful indexes on the join columns.
This post uses a concrete example to explain how a hash join works. The example is run on PostgreSQL 18.
Pavlo Golub: Contributions for week 42, 2025
Belgium Meetup: Tuesday, 14 October 2025 - organized by Boriss Mejias & Stefan Fercot
Speakers:
- Niradj Selvam
- Stefan Fercot
Pavlo Golub: Contributions for week 41, 2025
Barcelona PostgreSQL User Group met on Tuesday, Oct 7, organized by Dave Pitts & Lauro Ojeda
Speakers - Dave Pitts - Lauro Ojeda
Ellyne Phneah released two books: * The Social Code: Building a PostgreSQL Community Wired for Belonging * Decode PostgreSQL: Understanding the World's Most Powerful Open-Source Database Without Writing Code
Laurenz Albe: Benefits of a DESCending index
© Tobi Albe 2025
PostgreSQL can scan B-tree indexes in both directions. That means that there is little need to create a index in descending order (one created with the DESC clause). However, there are some cases where you need a descending index. There are also some corner cases where a descending index performs better than an ascending one. Follow me to explore use cases for the DESC clause!
Gabriele Bartolini: Postgres in Kubernetes: the commands every DBA should know
For many Postgres DBAs, Kubernetes feels like a new, complex world. But what if your existing skills were the key to unlocking it? This article demystifies cloud-native Postgres by revealing a first handful of kubectl and kubectl cnpg commands that act as your direct translator. I’ll move past the intimidating YAML to focus on the practical, imperative commands you’ll actually use to troubleshoot, inspect, and even perform a production switchover.
Paolo Melchiorre: Install PostgreSQL 18 on Ubuntu 25.10
How-to guide for installing PostgreSQL version 18 on Ubuntu, after a fresh installation of version 25.10 (Questing Quokka).
Paul Ramsey: PostGIS Performance: pg_stat_statements and Postgres tuning
In this series, we talk about the many different ways you can speed up PostGIS. Today let’s talk about looking across the queries with pg_stat_statements and some basic tuning.
Showing Postgres query times with pg_stat_statementsA reasonable question to ask, if you are managing a system with variable performance is: “what queries on my system are running slowly?”
Henrietta Dombrovskaya: Check out my new repo: logs_processing
I finally shared the set of functions that I use to process pgBadger raw output.
There will be more documentation, I promise, but at least the code is there, along with two of many presentations.
Ian Barwick: PgPedia Week, 2025-10-12
Ibrar Ahmed: Scaling Postgres
Postgres has earned its reputation as one of the world's most robust and feature-rich open-source databases. But what happens when your application grows beyond what a single database instance can handle? When your user base explodes from thousands to millions, and your data grows from gigabytes to terabytes?This is where Postgres scaling becomes critical. The good news is that Postgres offers multiple pathways to scale, each with its own advantages and use cases.
Tom Kincaid: Part 2: PostgreSQL’s incredible trip to the top with developers
In August of this year, I published a blog entitled PostgreSQL’s incredible trip to the top with developers which shows how Postgres has become the most used, most loved and most desired database according to the Stack Overflow annual developer survey. In that blog I said, I want to do the series in two parts. After some thought, I have decided to make it a 3 part series. It will break down as follows:
Tom Kincaid: Part 2: Postgres incredible journey to the top with developers.
In August of this year, I published a blog entitled PostgreSQL’s incredible trip to the top with developers which shows how Postgres has become the most used, most loved and most desired database according to the Stack Overflow annual developer survey. In that blog I said, I want to do the series in two parts. After some thought, I have decided to make it a 3 part series. It will break down as follows:
Sergey Solovev: Create and debug PostgreSQL extension using VS Code
In this tutorial we will create PostgreSQL extension ban_sus_query. It will check that DML queries contain predicates, otherwise will just throw an error.
Next, in order not to mislead up, I will use term contrib for PostgreSQL extension, and for extension for PostgreSQL Hacker Helper VS Code extension.
Sergey Solovev: Create and debug PostgreSQL extension using VS Code
In this tutorial we will create PostgreSQL extension ban_sus_query. It will check that DML queries contain predicates, otherwise will just throw an error.
Next, in order not to mislead up, I will use term contrib for PostgreSQL extension, and for extension for PostgreSQL Hacker Helper VS Code extension.
