Infrastructure at your Service
It’s been a while since I wrote the blog post about PostgreSQL 13 and Patroni 2.0. On this blog I received a comment, if it’s possible to explain, how to upgrade from Patroni 1.6 to 2. So let’s make a short blog about the upgrade procedure of Patroni.
PostgreSQL version 15 is on its way and we get a better and better look, what will be included in the future release. So it’s time to have a look at some new future features
In our blogs we already talked about Migrating a CentOS 7 EC2 instance to Rocky Linux 8 and CentOS 8 machine to Red Hat 8 , but how does it look like if you want to migrate your CentOS8 machine to AlmaLinux 8?
Have you ever asked yourself, how to create a second Patroni PostgreSQL cluster on an existing server using the existing etcd? My first idea was to study the documentation of Patroni, but unfortunately without big success. This post should help to identify the changes you have to do on the hosts to run two parallel Patroni clusters using an existing etcd.
Almost all of us, who already installed Enterprise DB Tools on a Linux server know the procedure. You need to add the EDB Repository to your server or your Red Hat Satellite configuration and after that you can easily install the tools you need. But what happens, if you are not able to add the repository? The answer is really simple: Download the rpms and install them directly on the server.
Starting with PostgreSQL 13 there is a name and value change of one of the parameters used for the streaming replication of a replica server. Some may already know which parameter I am talking about. Until Postgres 12 it was called “wal_keep_segments” but with PostgreSQL 13 it will become “wal_keep_size”. In this small post I will explain, what changed and which nice new feature Patroni 2.0 offers us to not get in trouble using old…
Last week the new Patroni 2.0 release was published which brings many new features. But one makes me absolutely curious. At the moment only as BETA, but I had to test it. Patroni on pure Raft. It’s possible to run Patroni without 3rd party dependencies. So no Etcd, Consul or Zookeeper is needed anymore. Great improvement! In this blog we will have a look at the setup and try an failover as well.
AWS comes with the great service of auto scaling, that gives the possibility to automatically adapt the environment to the changing needs. This helps to optimize costs and performance. With rising needs, your environment scales up and as soon as the needs decrease again, your environment will scale down again.
In my last post, I explained, how to setup a HA Postgres Cluster using EDB Postgres Advanced Server and Failover Manager. As a next step, we want to install the EDB Postgres Enterprise Manager to monitor what we setup before.
Some time ago I had a customer looking for a two node PostgreSQL Master/Replica solution. As we need Oracle compatibility in a later step, we decided to go with the EnterpriseDB tools. This article should give you an introduction on how to setup the environment.
