As far as i know, repmgr work at the "cluster" level so you would need
to run another postgres "cluster" instance (running on another port)
and another repmgrd instance (which would load a configuration
pointing to the new "cluster").
Regards,
Nicolas KAROLAK | Linux Systems Engineer
6-8, rue Andr
On Tue, 8 Jan 2019 at 06:45, Mitar wrote:
> So it could learn that the values used are not distinct values, or
> that column values are not uniformly distributed? And maybe decide to
> change the plan? So it makes a plan, runs it, determines that the plan
> was not as good as expected, I run it ag
As is often the case, I'm unsure of which of these methods to use, or if
I'm using them correctly.
PG10.5, jooq-3.10.8, postgresql-42.1.4, linux (redhat 6.9) and logback
to a file.
I have been using close() for a while but thought I would make use of
either the returned long from endCopy() o
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
Hi there,
I have following setup:
- master database, 9.5.7, on I386 (Pentium M),
now i want to replicate database to:
- slave database. 9.5.7 on armhf (OrangePiPC+).
Is in possible?
I already followed "replication setup"
https://www.howtoforge.com/tutorial/postgresql-replication-on-ubuntu-15-04/
