Daniel Westermann

8000 databases in one PostgreSQL cluster?

A while ago I posted this tweet on Twitter: #Postgresql friends: 8000 databases. One cluster, 8000 clusters, Kubernetes,, what would be your choice? Let's assume 10gb per database. I know backup/restore, inodes etc, no discussions about(…)

An introduction into server side programming in PostgreSQL – 3 – PL/pgSQL, procedures

In the first to posts in this series (An introduction into server side programming in PostgreSQL – 1 – SQL functions, basics , An introduction into server side programming in PostgreSQL – 2 –(…)

An introduction into server side programming in PostgreSQL – 2 – SQL functions, sets, udts and polymorphic types

This is part two of the little series about server side programming in PostgreSQL. In the last post we had a look at the basics when it comes to SQL functions. We learned how to write those(…)

An introduction into server side programming in PostgreSQL – 1 – SQL functions, basics

Over the last years I've seen many different applications running against PostgreSQL. The use cases vary from simple applications, which only use basic data types and a few tables and views, to complex applications with custom types, more specific data(…)

Dealing with German “Umlaute” in PostgreSQL’s full text search

PostgreSQL comes with build-in Full Text Search and you can do quite amazing stuff with it. A question that popped up during one of the last PostgreSQL for developers workshop was: How(…)

Cluster level encryption for PostgreSQL 14

The discussions how and why TDE (Transparent data encryption) should be implemented in PostgreSQL goes back several years. You can have a look at these two more recent threads to get an idea on how much discussion happened around that(…)

pg_auto_failover: Failover and switchover scenarios

In the last post we had a look at the installation and setup of pg_auto_failover. We currently have one primary cluster and two replicas synchronizing from this primary cluster. But we potentially also have an issue(…)

Easy failover and switchover with pg_auto_failover

One the really cool things with PostgreSQL is, that you have plenty of choices when it comes to tooling. For high availability we usually go with Patroni, but there is also pg_auto_failover(…)

Incremental materialized view maintenance for PostgreSQL 14?

Since PostgreSQL 9.3 there is the possibility to create materialized views in PostgreSQL. PostgreSQL 9.4 (one year later) brought concurrent refresh which already is a major step forward as this allowed querying(…)

Even faster data loading with PostgreSQL 14? wal_level=none

PostgreSQL is already very fast with loading loading large amounts of data. You can follow this post to get some recommendations for loading data as fast as possible. In addition you can create(…)