Archive

GoldenGate 26ai AutoSchema TYPEMAP: overriding the default datatype mapping

In my blog about the new automatic schema evolution feature in GoldenGate 26ai, I was replicating the following table from Oracle to PostgreSQL: CREATE TABLE autosch.t1 ( id NUMBER PRIMARY KEY, name VARCHAR2(50), amount NUMBER(10,2),(…)

GoldenGate 26ai automatic schema evolution: creating missing tables during an initial load

For as long as I have used GoldenGate, an initial load had one prerequisite: the target tables must already exist. Data Pump takes care of it between two Oracle databases. For anything else, you write the CREATE TABLE statements(…)

AI problems are database problems

Introduction When discussing agentic AI, we spend a lot of time on the model. Which one should we use? How much context does it support? Can it choose the right tool? These are useful questions. But from a my(…)

PostgreSQL Snapshot Backup and Restore with Proxmox ZFS (4/4)

In the blog series I previously wrote, I did not answer all the customer’s questions. The last one was the following: Can this also be applied to PostgreSQL? In short, yes, it is possible. Let’s see(…)

Highly Available, Load-Balanced PostgreSQL with Patroni, HAProxy, and Keepalived

Patroni runs your PostgreSQL cluster and handles failover, promoting a replica the moment the primary dies and recording the change in its distributed store (etcd, Consul, or ZooKeeper). That part works on its own. Your applications still need(…)

Upgrade RHEL from 9.6 to 10.1 (when running PostgreSQL/Patroni)

Upgrading from RHEL 9.6 to 10.1 is not just a routine update, it’s a major platform shift. When your server runs PostgreSQL compiled from source and a Patroni-managed cluster, the complexity increases significantly. System libraries change, Python environments break,(…)

PostgreSQL 19: Dynamically adjust the I/O worker pool

When PostgreSQL 18 was released last year one of the major features was the introduction of the asynchronous I/O subsystem. The main configuration parameter for this was (and still is)(…)

PostgreSQL 19: Importing statistics from remote servers

Usually we do not see many foreign data wrappers being used by our customers. Most of them use the foreign data wrapper for Oracle to fetch data from Oracle systems. Some of them use the(…)

PostgreSQL 19: Online enabling of data checksums

Since PostgreSQL 18 was released last year checksums are enabled by default when a new cluster is initialized. This also means, that you either need to explicitly disable that when you upgrade from a previous version of PostgreSQL or(…)

PostgreSQL 19: get_*_ddl functions

PostgreSQL already comes with plenty of system information functions to reconstruct the commands to create various objects, e.g. constraints or indexes. Starting with PostgreSQL 19 more functions will be available, namely those: pg_get_database_ddl pg_get_role_ddl pg_get_tablespace_ddl(…)