Neues vom PostgreSQL Planet
Stefanie Janine Stölting: pgsql_tweaks Version 1.0.1 Released
-
pgsql_tweaks is a bundle of functions and views for PostgreSQL
-
Stefanie Janine Stölting: pgsql_tweaks Version 1.0.2 Released
-
pgsql_tweaks is a bundle of functions and views for PostgreSQL
-
Luca Ferrari: pgenv 1.4.3 is out!
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?
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
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
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/OLet's dive into this and understand what the fuzz is all about. The standard I/O model works roughly like this:
Pavlo Golub: pgwatch v4-beta is out!
pgwatch v4? Yes, after a long time of silence, we are finally releasing a new major version!
Why version 4?What happened to pgwatch v3!? It was released less than a year ago!
If Firefox can have version 142 and Chrome version 139 (and those numbers are probably already outdated by the time of publishing), why should we care about strict versioning? 🙂
On a more serious note, we decided to stick to the PostgreSQL major versioning scheme, so pgwatch major releases will now follow PostgreSQL major releases.
Henrietta Dombrovskaya: September PUG recording
I am glad we had an option to replay this talk from PG Day Chicago one more time! If you didn’t have a chance to join us, here is the recording – enjoy!
Hubert 'depesz' Lubaczewski: Waiting for PostgreSQL 19 – Add date and timestamp variants of random(min, max).
On 9th of September 2025, Dean Rasheed committed patch: Add date and timestamp variants of random(min, max).Paul Ramsey: 2025 PostGIS & GEOS Release
I am excited to announce PostGIS 3.6 and GEOS 3.14.
The PostGIS spatial extension to PostgreSQL and the GEOS computational geometry library taken together provide much of the functionality of PostGIS, and are the open source focus of the (Crunchy Data) Snowflake PostGIS team.
Esther Minano: Making Postgres scale to zero with CNPG
How we built activity-aware Postgres clusters that hibernate automatically and save resourcesFloor Drees: Contributions for the week 37
Miles Richardson presented the WarehousePG project (an open source Greenplum fork) at the Apache Iceberg™ Europe Community Meetup in London, September 8. Watch the recording: youtu.be/lz6w9W1Ubps?si=upETJvoKD_zuHL0R
PGDay UK took place, September 9, at the Cavendish Conference Center.
Organizers:
- Chris Ellis
- Devrim Gunduz
- Dave Page
Talk Selection Committee:
Ants Aasma: Reconsidering the interface
Recently a great presentation “1000x: The Power of an Interface for Performance” from Joran Dirk Greef from TigerBeetle made the rounds. If I may summarize, the gist of the presentation was that the correct programming model can mean many orders of magnitude performance difference. As the presentation did not explore this, I wanted to see how far we get by adjusting our programming style on boring old relational databases.
Ian Barwick: PgPedia Week, 2025-09-07
PostgreSQL 19 changes this week New GUC debug_print_raw_parse Option max_retention_duration added for subscriptions COPY : hint added for COPY TO when a WHERE clause was provided, noting that COPY (SELECT ... WHERE ...) TO can be used instead PostgreSQL 18 changes this weekPostgreSQL 18 RC1 has been released ( announcement ).
Laurenz Albe: How to handle "database is not accepting commands"
© Laurenz Albe 2025Stefanie Janine Stölting: pgsql_tweaks Version 1 Released!
-
pgsql_tweaks is a bundle of functions and views for PostgreSQL
-
Stefanie Janine: pgsql_tweaks 1.0.0 Released
pgsql_tweaks is a bundle of functions and views for PostgreSQLThe source code is available on Codeberg.
You can install the whole package, or just copy what is needed from the source code.The extension is also available on PGXN.
Version 1.0I decided to make this the 1.0 Version. The First commit is from 2017-08-11, the extension is now more than eight years old.
-
Ian Barwick: PgPedia Week, 2025-08-31
The PostgreSQL code base has been around for almost 3 decades, and as recent commit 710e6c43 shows, there is still some legacy cruft from the initial import/conversion in need of cleanup:
Remove unneeded casts of BufferGetPage() result BufferGetPage() already returns type Page, so casting it to Page doesn't achieve anything. A sizable number of call sites does this casting; remove that. This was already done inconsistently in the code in the first import in 1996 (but didn't exist in the pre-1995 code), and it was then apparently just copied around.
Mayur B.: Unsung Heros of Postgres : Episode I
Unsung Heros of Postgres : Episode INot all heroes wear capes. In PostgreSQL, some don’t even write code.
At PGDay Austria, Floor Drees highlighted this truth: countless contributions to PostgreSQL happen outside of code commits and patches.
Radim Marek: PostgreSQL maintenance without superuser
How many people/services have superuser access to your PostgreSQL cluster(s)? Did you ever ask why your software engineers might need it? Or your BI team? Why those use cases require same privileges as someone who can drop your databases?
The answer isn't because these operations are inherently dangerous - it's because PostgreSQL historically offered limited options for operational access or simply because not enough people are aware of the options. So the common practice is to either got basic permissions or handover the keys to the kingdom.
Seiten
-
pgsql_tweaks is a bundle of functions and views for PostgreSQL
-