Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kBXpy-0004Ln-8V for pgsql-admin@arkaria.postgresql.org; Fri, 28 Aug 2020 06:26:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kBXpx-0008QU-4D for pgsql-admin@arkaria.postgresql.org; Fri, 28 Aug 2020 06:26:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kBXpW-0002rX-Su for pgsql-admin@lists.postgresql.org; Fri, 28 Aug 2020 06:25:43 +0000 Received: from cloudearth.serversfarm.com ([216.244.65.90]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kBXpP-0007TF-B1 for pgsql-admin@postgresql.org; Fri, 28 Aug 2020 06:25:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ibosstech-us.com; s=x; h=Content-Type:Mime-Version:Reply-To:References: In-Reply-To:Message-Id:Date:Cc:Subject:To:From:Sender: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Q6Be0jianOApI3msJIlGGDE5vCJH3A694wg6VNR9q3Q=; b=1keBodew9BFyEG32KXzih0w5d +1CdfW5nFbT44iGkKAhBqv9tOwP0zeOnInG+k1PuNcyLoVpyfF2sn44yTvz1ZiPlgRbzq/q6EcwFo Rqcv9I+m0cfKcSjhrD6YDReJfq9eCVy9nwtXLxRKR5UiKahIuQmrcYmkd3U3f5V/3E5uzanULIMB+ tOI2vgFOFEFkdbXFTpJ0EiB9AkEMwR3d9Rexk8d001BKP3hlk/u1mFrLxNvphNiGCw6cMTyLMm8f4 kxV4/byBqcwVtHO+Qg9MYtZn+te8Tm8CeLu4916111aXoqyD8gnt+Xxqs1jeRCL9586plLgH2815A miEAa5MGw==; Received: from [223.190.96.74] (helo=[192.168.1.2]) by cloudearth.serversfarm.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1kBWrg-002ziZ-2h; Fri, 28 Aug 2020 01:23:52 -0400 From: "Anjul Tyagi" To: "Matthew Tice" Subject: Re: Logical Replication - Rep Manager Cc: pgsql-admin Date: Fri, 28 Aug 2020 05:23:31 +0000 Message-Id: In-Reply-To: References: <363131598424371@mail.yandex.com.tr> Reply-To: "Anjul Tyagi" User-Agent: eM_Client/8.0.3385.0 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MBF885C29D-C954-420C-B784-B37C3C0D8B6B" X-Authenticated-Id: anjul@ibosstech-us.com List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --------=_MBF885C29D-C954-420C-B784-B37C3C0D8B6B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Matthew, thanks for the information. Yes we are using the replication slot for=20 that. is there any alternate for that? Regards, Anjul TYAGI =C3=BC Go Green ------ Original Message ------ From: "Matthew Tice" To: Cc: "pgsql-admin" 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=20 >standby database. They would need to be re-created upon standby=20 >promotion. > >On Wed, Aug 26, 2020 at 6:23 AM Anjul Tyagi =20 >wrote: >>Samed, >> >>i tied the same, unfortunate it did not work. after promoting we have=20 >>seen error log, replication slot is not exist. I tried to start the=20 >>slot but did not work. >> >> >> >> >>Regards, >> >>Anjul TYAGI >> >> >> >>=C3=BC Go Green >> >> >>------ Original Message ------ >>From: "Samed YILDIRIM" >>To: "Anjul Tyagi" ; "pgsql-admin"=20 >> >>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=20 >>>may solve your issue. >>> >>>For example; >>>create subscription sub1 >>> connection 'host=3D192.168.100.25,192.168.100.50,192.168.56.20=20 >>>dbname=3Dprod_db user=3Dlogical_rep password=3D123' >>> publication pub_for_report; >>> >>>https://www.postgresql.org/docs/12/libpq-connect.html#LIBPQ-MULTIPLE-HOS= TS >>> >>>Best regards. >>>Samed YILDIRIM >>> >>>25.08.2020, 20:34, "Anjul Tyagi" : >>>>Hi Team, >>>> >>>>We are planning to implement the Rep Manager in our environment to=20 >>>>manage the replication. While reading the documentation we found out=20 >>>>that if primary goes down. We can promote one of the standby server=20 >>>>and make it primary. However we have one reporting server that we=20 >>>>are replicating specific table data via logical replication. While=20 >>>>doing testing in lower environment, we noticed when we primary goes=20 >>>>down and we promote the standby server, our replication also breaks.=20 >>>>Do we have any option and suggestion to handle the logical=20 >>>>replication in case of failure. >>>> >>>>Thanks in advance. >>>> >>>> >>>> >>>> >>>>Regards, >>>> >>>>Anjul TYAGI >>>> >>>> >>>> >>>>=C3=BC Go Green >>>> >>>> --------=_MBF885C29D-C954-420C-B784-B37C3C0D8B6B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Matthew,
thanks for the information. Yes we are using the replication = slot for that.=C2=A0

is there any alternate for = that?

=C2=A0
=C2=A0
=C2=A0

Regards,

Anjul TYAGI

=C2=A0

=C3=BC<= /b>=C2=A0Go=C2= =A0Green


------ Original Message ------
From: "Matthew Tice" <mjtice@gm= ail.com>
To:
Cc: "pgsql-admin" <pg= sql-admin@postgresql.org>
Sent: 8/27/2020 10:27:54 PM
Subject: Re: Logical Replication - Rep Manager

Are you using a replication_slot? =C2=A0

<= div>If so, as I understand, replication_slots are not replicated to the sta= ndby database.=C2=A0 They would need to be re-created upon standby promotio= n.

On Wed, Aug 26, 2020 at 6:23 AM Anjul Tyagi <anjul@ibosstech-us.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pa= dding-left:1ex">
Samed,

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

=C2=A0
=C2=A0
=C2=A0

R= egards,

A= njul TYAGI

=C2=A0<= /u>

=C3=BC=C2=A0Go=C2=A0Green


=
------ Original Message ------
From: "Samed YILDIRIM" <samed@r= eddoc.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,
=C2=A0
I haven't tested, but specif= ying multiple host in connection string may solve your issue.
=C2= =A0
For example;
create subscription sub1
=C2= =A0 =C2=A0 =C2=A0 connection 'host=3D192.168.100.25,192.168.100.50,192.168.= 56.20 dbname=3Dprod_db user=3Dlogical_rep password=3D123'
=C2=A0 = =C2=A0 =C2=A0 publication pub_for_report;
=C2=A0
=C2=A0
Best regards.
Samed Y= ILDIRIM
=C2=A0
25.08.2020, 20:34, "Anjul Tyagi" <anjul@ibosstech-us.com>:
Hi Team= ,
=C2=A0
We are planning to implement the Rep Manager i= n our environment to manage the replication. While reading the documentatio= n 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 a= re replicating specific table data via logical replication. While doing tes= ting in lower environment, we noticed when we primary goes down and we prom= ote the standby server, our replication also breaks. Do we have any option= and suggestion to handle the logical replication in case of failure.
<= div>=C2=A0
Thanks in advance.=C2=A0
=C2=A0
=C2=A0
=C2=A0
=C2=A0

Reg= ards,

Anjul = TYAGI

=C2=A0

=C3=BC= =C2=A0Go=C2=A0Green

=C2=A0
--------=_MBF885C29D-C954-420C-B784-B37C3C0D8B6B--