This is the bug reporting address, and what you are writing is not a bug
report.
What you are asking about is very complex and will probably involve many
different software components with specific configurations and
nontrivial interactions. That's not something someone can answer in a
single email in their discretionary time. I think you need to do some
more research on your own or hire some help.
On 09.01.22 09:18, Padmakumar Kadayaprth wrote:
> Dear All,
> I am not sure this is the mailing list to which I have to send
> this issue.If you know the correct mailing address please let me know or
> forward this mail to that address.
>
> Issue i am facing is as follows
> I am on Ubuntu ,postgresql 14 pglogical for postgres 14
>
> I have 35 branches and one regional site. All branches including
> regional sites have it's own transaction.
> All Transaction from branches will be replicated to regional using
> pglogical. Almost 50 Tables out of 350 tables.entire tables in the
> database are not replicated.
>
> Now I need high availability in all branches and regional sites, which
> is the best open source solution available with postgreSQL. In case of
> failover to secondary, how I will reroute my replication to regional
> without manual intervention.How I will make sure /control replication
> from branches to regional are happening only from current primary.
>
> which is the pooling /load balancing and virtual IP solution compatible
> with my solution using which i can connect to current primary in case of
> failover from application
>
> Thanks,
> Padmakumar
>