Re: Logical Replication - Rep Manager

Samed,

i tied the same, unfortunate it did not work. after promoting we have
seen error log, replication slot is not exist. I tried to start the slot
but did not work.

Regards,

Anjul TYAGI

ü Go Green

------ Original Message ------
From: "Samed YILDIRIM" <samed(at)reddoc(dot)net>
To: "Anjul Tyagi" <anjul(at)ibosstech-us(dot)com>; "pgsql-admin"
<pgsql-admin(at)postgresql(dot)org>
Sent: 8/26/2020 12:20:29 PM
Subject: Re: Logical Replication - Rep Manager

>Hi Anjul,
>
>I haven't tested, but specifying multiple host in connection string may
>solve your issue.
>
>For example;
>create subscription sub1
> connection 'host=192.168.100.25,192.168.100.50,192.168.56.20
>dbname=prod_db user=logical_rep password=123'
> publication pub_for_report;
>
>https://www.postgresql.org/docs/12/libpq-connect.html#LIBPQ-MULTIPLE-HOSTS
>
>Best regards.
>Samed YILDIRIM
>
>25.08.2020, 20:34, "Anjul Tyagi" <anjul(at)ibosstech-us(dot)com>:
>>Hi Team,
>>
>>We are planning to implement the Rep Manager in our environment to
>>manage the replication. While reading the documentation we found out
>>that if primary goes down. We can promote one of the standby server
>>and make it primary. However we have one reporting server that we are
>>replicating specific table data via logical replication. While doing
>>testing in lower environment, we noticed when we primary goes down and
>>we promote the standby server, our replication also breaks. Do we have
>>any option and suggestion to handle the logical replication in case of
>>failure.
>>
>>Thanks in advance.
>>
>>
>>
>>
>>Regards,
>>
>>Anjul TYAGI
>>
>>
>>
>>ü Go Green
>>
>>