From: Anjul Tyagi <anjul@ibosstech-us.com>
To: Matthew Tice <mjtice@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Logical Replication - Rep Manager
Date: Fri, 28 Aug 2020 05:23:31 +0000
Message-ID: <em97543702-afd2-4d2c-85ea-dbf451212b0f@iboss01108> (raw)
In-Reply-To: <CA+taBv_06K5=7PDqk3qsvkHsc4UfyvWf=W7X26qAgLu8=HA+ZQ@mail.gmail.com>
References: <ema35a8831-3413-4c3d-999d-a2ef2d0f4aa0@iboss01108>
<363131598424371@mail.yandex.com.tr>
<em70d68d70-4c04-442f-97c2-992372929b3c@iboss01108>
<CA+taBv_06K5=7PDqk3qsvkHsc4UfyvWf=W7X26qAgLu8=HA+ZQ@mail.gmail.com>
Matthew,
thanks for the information. Yes we are using the replication slot for
that.
is there any alternate for that?
Regards,
Anjul TYAGI
ü Go Green
------ Original Message ------
From: "Matthew Tice" <mjtice@gmail.com>
To:
Cc: "pgsql-admin" <pgsql-admin@postgresql.org>
Sent: 8/27/2020 10:27:54 PM
Subject: Re: Logical Replication - Rep Manager
>Are you using a replication_slot?
>
>If so, as I understand, replication_slots are not replicated to the
>standby database. They would need to be re-created upon standby
>promotion.
>
>On Wed, Aug 26, 2020 at 6:23 AM Anjul Tyagi <anjul@ibosstech-us.com>
>wrote:
>>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@reddoc.net>
>>To: "Anjul Tyagi" <anjul@ibosstech-us.com>; "pgsql-admin"
>><pgsql-admin@postgresql.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@ibosstech-us.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
>>>>
>>>>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: anjul@ibosstech-us.com, mjtice@gmail.com
Subject: Re: Logical Replication - Rep Manager
In-Reply-To: <em97543702-afd2-4d2c-85ea-dbf451212b0f@iboss01108>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox