Daniel Westermann

Using dlt to get data from Db2 to PostgreSQL

For a recent project at one of our customers we needed to get data from a Db2 database into PostgreSQL. The first solution we thought of was the foreign data wrapper for Db2. This is usually(…)

2025.pgconf.de recap

( note: I am writing this as member of the pgconf.de organization team, and not as a dbi services employee ) After almost half a year of planning and preparation PostgreSQL Conference Germany 2025 finally took(…)

Getting started with Open WebUI

Everybody is talking about AI, RAG and language models today. A lot of people are using ChatGPT or other tools to get answers(…)

PostgreSQL 18: Support for asynchronous I/O

This is maybe one the biggest steps forward for PostgreSQL: PostgreSQL 18 will come with support for asynchronous I/O. Traditionally PostgreSQL relies on the operating system to hide the latency of writing to disk, which is done synchronously and can(…)

PostgreSQL 18: Add function to report backend memory contexts

Another great feature was committed for PostgreSQL 18 if you are interested how memory is used by a backend process. While you can take a look at the memory contexts for your current session since PostgreSQL 14, there was no(…)

PostgreSQL 18: Allow NOT NULL constraints to be added as NOT VALID

Before we take a look at what this new feature is about, let’s have a look at how PostgreSQL 17 (and before) handles “NOT NULL” constraints when they get created. As usual we start with a simple table: postgres=# select(…)

PostgreSQL 18: “swap” mode for pg_upgrade

When you want to upgrade from one major version of PostgreSQL to another you probably want to go with pg_upgrade (or logical replication). There are several modes of operations for this already: –copy: Copy the data(…)

PostgreSQL 18: Add “–missing-stats-only” to vacuumdb

Loosing all the object statistics after a major version upgrade of PostgreSQL with pg_upgrade is one of the real paint points in PostgreSQL. Collecting/generating the statistics can take much longer than the actual upgrade which is quite painful. A(…)

PostgreSQL 18: More granular log_connections

Many of our customers enable log_connections because of auditing requirements. This is a simple boolean which is either turned on or off. Once this is enabled and active every new connection to a PostgreSQL database is(…)

PostgreSQL: Unlogged tables and backups

Recently we faced the following situation and have been asked to analyze the issue: A dump was loaded into a primary instance of PostgreSQL, but the data did not reach the replica. Tables which have been added after the dump(…)