Neues vom PostgreSQL Planet

Our reaction to the PostgreSQL benchmarks published by PlanetScale and the results of running them against a Xata instance.

One of our customers recently asked if they could use their Python application built with SQLAlchemy with pgEdge, and were pleased to learn that they could. But what is SQLAlchemy, and what considerations might there be when working with a distributed multi-master PostgreSQL cluster like pgEdge Distributed Postgres?SQLAlchemy is “the Python SQL Toolkit and Object Relational Mapper” according to its website.

Switching the PostgreSQL Conference Calendar Location Currently Calendar Location

So far the conference calendars in https://proopensource.it/conference-calendar/ have been stored in Google Calendar.

As that is a foreign ressource, I decided to move them away from Google.

Storing and archiving data efficiently

When it comes to designing and optimizing databases, one of the most critical aspects is the choice of storage options. PostgreSQL, like many other relational databases, provides various storage options that can significantly impact performance, data integrity, and overall database efficiency.

At this year’s PGConf.dev, the premier gathering for PostgreSQL contributors, developers, and community leaders, Zhijie Hou and I had the opportunity talk about the challenges and solutions around conflict handling in logical replication — a topic increasingly rele

Since our last public update, OrioleDB has continued to evolve with a series of new releases. These updates refine the core engine, extend functionality, and improve performance across a range of workloads. Together, they move us closer to a beta release and lay the groundwork for broader adoption.

Some weeks ago Postgres (well, not directly the official Postgres project) again managed to surprise me during my daily muscle-memory operations, prompting even one relatively lazy human to actually write about it. So while minding some other common Postgres business, I double-tapped “Tab” to complete on “pg_v”, looking for pg_verifybackup...

PostgreSQL Person of the Week Interview with Dian Fay: I live in Michigan with my partner Trent, a cat named Bread, and a tarantula named Carmilla. I’m originally from the Florida panhandle, but I moved up here for school lo these many years ago and wound up sticking around – it’s nice having seasons. My mother taught me how to type on her old Selectric when I was six or seven (my handwriting never recovered), and my father taught me BASIC when I was eight by copying code listings out of his Sky & Telescope magazines. In other words, I never stood a chance.

PostgreSQL 19 changes this week new system view pg_dsm_registry_allocations the LSN output format is now uniformly set to %X/%08X this also affects the pg_lsn datatype, with e.g. SELECT '0/0'::pg_lsn returning 0/00000000 (in PosgreSQL 18 and earlier: 0/0 ). the CHECKPOINT command now accepts the following options: FLUSH_UNLOGGED [ boolean ] MODE { FAST | SPREAD } new libpq connection parameter servicefile added PostgreSQL 18 changes this week

PostgreSQL 18 beta2 is will likely be released on July 17th (Thursday): 18beta2 next week .

The cooperative company DALIBO is celebrating its 20th anniversary today, giving me an opportunity to reflect on the reasons behind the success of this collective adventure.

PUG Stuttgart

PUG Stuttgart happened on June, 26th - hosted by Aleshkova Daria

At my day job, we use row-level security extensively. Several different roles interact with Postgres through the same GraphQL API; each role has its own grants and policies on tables; whether a role can see record X in table Y can depend on its access to record A in table B, so these policies aren't merely a function of the contents of the candidate row itself. There's more complexity than that, even, but no need to get into it.

Two tables, then.

Vibhor Kumar and Marc Linster; last updated July 10 2025

Progress on ABI Compliance Reporting with BuildFarm

When implementing an optimization for derived clause lookup myself, Amit Langote and David Rowley argued about the initial size of hash table (which would hold the clauses). See some discussions around this email on pgsql-hackers.

Data is a key part of any mission-critical application. Losing it can lead to serious issues, such as financial loss or harm to a business’s reputation. A common way to protect against data loss is by taking regular backups, either manually or automatically. However, as data grows, backups can become large and take longer to complete. If these backups are not managed properly or tested often, a sudden system crash could result in permanent data loss.

In Part 1 of this series, we discussed what active-active databases are and identified some “good” reasons for considering them, primarily centered around extreme high availability and critical write availability during regional outages. Now, let’s turn our attention to the less compelling justifications and the substantial challenges that come with implementing such a setup.

Last week I posted about how we often don’t pick the optimal plan. I got asked about difficulties when trying to reproduce my results, so I’ll address that first (I forgot to mention a couple details). I also got questions about how to best spot this issue, and ways to mitigate this. I’ll discuss that too, although I don’t have any great solutions, but I’ll briefly discuss a couple possible planner/executor improvements that might allow handling this better.

PostgreSQL Person of the Week Interview with Josef Machytka: I was born in Czechia and lived most of my life there. However, for the last 12 years, my family and I have been calling Berlin, Germany, our home. It is an open-minded place that gives people a lot of freedom, we like it here very much.

PostgreSQL 19 development is now officially under way, so from now on any new features will be committed to that version. Any significant PostgreSQL 18 changes (e.g. reversions or substantial changes to already committed features) will be noted here separately (there were none this week).

PostgreSQL 19 changes this week

The first round of new PostgreSQL 19 features is here: