Re: multiple configurations with repmgr

From: Martín Marqués <martin(at)2ndquadrant(dot)com>
To: ROS Didier <didier(dot)ros(at)edf(dot)fr>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: multiple configurations with repmgr
Date: 2019-01-09 17:23:35
Message-ID: 529b85d5-5137-3e66-6428-febc3c96a997@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

El 8/1/19 a las 13:17, ROS Didier escribió:
> Hi
>
>                We are going to use repmgr  with one node for the
> primary, one node for the standby and one node for the witness.
>
>                It works fine _with one project_.
>
>  
>
> The problem is  that we want to have several other projects. Each one
> with its own primary node, its own standby node and the _same witness node._
>
>                Question : is it possible to do that ? _One witness node_
> which surveys several other nodes.

Yes, you can accomplish that following the instructions below for
configuring the witness:

- Initialize the postgres server on the witness node
- Create one database for each cluster the witness will be managing
- Create the appropriate repmgr.conf files, one for each cluster managed
through this witness, and each with the appropriate conninfo setting so
they point to different databases.
- Run `repmgr witness register` multiple times, using different
configuration files on each run

Hope that helps clarify.

P.S.: This works on latest versions of repmgr. Before 3.3 the witness
was created through repmgr which made things harder to manage, reason
why that was removed in later versions

Cheers,

--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mark Fletcher 2019-01-09 17:24:18 Re: Pulling data from Postgres DB table for every 5 seconds.
Previous Message github kran 2019-01-09 17:21:57 Re: Pulling data from Postgres DB table for every 5 seconds.