Clarification related to BDR
Hi, I came across a link published in postgresql, where it is clearly mentioned BDR as an open source. When I tried to install BDR for CentOS from 2ndQuadrant, the yum repository was not reachable and upon further enquiring with 2ndQuadrant, I got a reply from them quoting as follows "BDR is not open source. We do not have plans to open source this." Can you please help me understand, why the following news is published in "postgresql" with an encouraging message acknowledging BDR as an open source? We invested time and effort to use BDR only to understand at a later point in time, that it is not. Kindly clarify, if I am missing anything. https://www.postgresql.org/about/news/1689/ [image: image.png] Regards, KRS
Configuring more than one hot standby server
Hi Community, I read about "hot stand by" server and as far as the document goes, it does not explicitly explain about, whether is it possible to configure more than on database as a Hot stand by server. If we can configure more than one hot stand by server, which database will take the role of master, in case the original master instance crashes? Does a leader election happen? Regards, KRS
Clarification relation logical replication
Hi, Can I have a cluster of multiple instances with logical replication enabled for all tables with every single instance as both publisher and subscriber, to mimic multi master replication? The documentation says, care must be taken on subscribed publication objects to not overlap? Ref : https://www.postgresql.org/docs/12/logical-replication-subscription.html "A subscriber node may have multiple subscriptions if desired. It is possible to define multiple subscriptions between a single publisher-subscriber pair, in which case care must be taken to ensure that the subscribed publication objects don't overlap." If the above multi master scenario is not possible in logical replication, and if is one publisher and multiple subscribers, what will happen if the publisher instance crashes? How to enable hot standby in cluster setup where there is one publisher of logical replication and rest all instances are subscribers? Regards, KRS
Behaviour of failed Primary
Hi Forum, If I have a cluster with Synchronous replication enabled with three nodes, for eg: [primary] [hot stand by 1] [host stand by 2] And for some unforeseen reasons, if primary fails, the failover will kick in and hot stand by 1 will become new primary and cluster setup will look like this [new primary (hot stand by1)] [host stand by 2] My question here is, what will happen if the original primary which has failed comes back. Will it become part of this high available replica cluster automatically or it will be stale and disconnected from the cluster? How can we automatically make the failed primary to be part of the cluster with hot standby role? It would be of great help, if you can direct me to any references details. Thank you, upfront. Regards, Santhosh
