On Fri, Sep 04, 2020 at 05:24:00PM -0400, Digimer wrote:
> It would depend on AWS, and I don't believe it's a good idea to design a
> solution that depends on a third party's behaviour.
It would be strange if AWS control API for node1 would be serialized with
control for node2. In fact fence_aws
On 2020-09-04 5:15 p.m., Philippe M Stedman wrote:
> Hi ClusterLabs development,
>
> I am in the process of deploying a two-node cluster on AWS and using the
> fence_aws fence agent for fencing. I was reading through the following
> article about common pitfalls in configuring two-node Pacemaker
Hi ClusterLabs development,
I am in the process of deploying a two-node cluster on AWS and using the
fence_aws fence agent for fencing. I was reading through the following
article about common pitfalls in configuring two-node Pacemaker clusters:
On Fri, 4 Sep 2020 10:55:31 +0200
Oyvind Albrigtsen wrote:
> Add the "recovery.conf" parameters to postgresql.conf (except the
> standby one) and touch standby.signal (which does the same thing).
+1
> After you've verified that it's working and stop PostgreSQL you simply
> rm standby.signal
Add the "recovery.conf" parameters to postgresql.conf (except the
standby one) and touch standby.signal (which does the same thing).
After you've verified that it's working and stop PostgreSQL you simply
rm standby.signal and the "recovery.conf" specific parameters, and the
resource agent will
Hello,
Please, can you provide example, explanation or give link to existing
documentation - how to use
pacemaker/corosync for HA Cluster for PostgreSQL 12.x?
Problem is what in PostgreSQL 12 file "recovery.conf" is deprecated, not used
now.
--
WBR,
Andrey Larionov
>>> Klaus Wenninger schrieb am 03.09.2020 um 18:20 in
Nachricht <8bef645e-5ac0-93c1-973c-2d0ed81b6...@redhat.com>:
...
> That btw. does at least in German exist as "Maschinenbett" as well.
It also exists as verb "betten" and in my understandingit can mean as much as
to "put in place". So maybe
