Skip to content

DBVISIT StandbyMP for PostgreSQL – 3 – Switchovers

In the last two posts (here and here) we’ve installed and configured DBVISIT StandbyMP for PostgreSQL and created a simple primary -> replica setup. Most of the replication setup was GUI driven and almost nothing had to be done manually, except for the creation of a user and configuration of pg_hba.conf. Currently we have the primary replicating to the replica and the StandbyMP management console managing this configuration:

One advantage of such a setup is, that the replica can take over the role of the primary and vice versa, e.g. when patching is required on one of the nodes. In StandbyMP this is called a “Graceful Switchover”, so lets try to do this and see what happens:

This takes a few second and the instances will have switched the roles:

The same works of course in the other direction.

Questions about your own setup? A dbi services consultant can look at your case.

Talk to an expert (opens in a new tab)

If you prefer a graphical user interface for setting up and operating a primary -> replica configuration, then this could be an option for you. It is really easy to setup and you don’t have to touch the command line.

Let’s work together

Ready to operate at
the next level?

Tell us about your challenge. We’ll bring the depth, the expertise, and the Swiss precision.

Open source Team

Open source Team

Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.View Author posts

721 posts since September 2011

Most read in Database

The Database posts our readers open most: the all-time favourites, and what is trending right now.

Leave a Comment

Your email address will not be published. Required fields are marked *