Daniel Westermann

temBoard on SLES15 – 1 – The WebUI

During our last SwissPUG online meeting there was a presentation about monitoring PostgreSQL with temBoard. A question that came up afterwards was: How to install that on SLES 15 as there(…)

PostgreSQL 14: LZ4 compression for TOAST

In PostgreSQL a row or tuple can not span multiple pages (a page is typically 8kB), but of course you can store larger rows and PostgreSQL brakes and compresses these rows into smaller chunks by using a technique called(…)

Getting started with the Zalando Operator for PostgreSQL

In the previous posts (Rancher, up and running, on EC2 – 1 – One node, Rancher, up and running, on EC2 – 2 – Three nodes, Rancher, up and running, on(…)

Deploying a Kubernetes cluster on EC2 with Rancher

Once Rancher is up and running, it makes the deployment and management of Kubernetes clusters quite easy. In this post we'll deploy a brand new cluster on top of EC2. If you want to have a simple(…)

Rancher on SLES 15 as a demo environment

If you followed the last posts (Rancher, up and running, on EC2 – 1 – One node, Rancher, up and running, on EC2 – 2 – Three nodes and Rancher,(…)

Rancher, up and running, on EC2 – 3 – Rancher setup

The is the next post in this little Rancher series. After we installed a single node RKE cluster and extended this configurtation to three nodes we will finally install Rancher in this post.

Rancher, up and running, on EC2 – 2 – Three nodes

In the last post we've brought up a RKE Kubernetes cluster on a single node. While that is cool for demonstration purposes or testing, this is nothing for a real life setup. Running the control pane, the(…)

Rancher, up and running, on EC2 – 1 – One node

If you want to play with Rancher you have several options, as outlined in the documentation. There are quick starts for the major public cloud providers (using Terraform), you can install(…)

Be careful with prepared transactions in PostgreSQL

PostgreSQL gives you the possibility for two-phase commit. You'll might need that if you want an atomic distributed commit. If you check the PostgreSQL documentation there is a clear warning about using these kind(…)

[Data]nymizer – Data anonymizer for PostgreSQL

Often there is the requirement to populate a test or development database with data from production, but this comes with a risk: Do you really want, that developers or testers have access to sensitive data? In a lot of companies(…)