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 1n7bcU-0006xq-GM for pgsql-bugs@arkaria.postgresql.org; Wed, 12 Jan 2022 11:16:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n7bcT-0000gB-4Y for pgsql-bugs@arkaria.postgresql.org; Wed, 12 Jan 2022 11:16:45 +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 1n7bcS-0000g2-SD for pgsql-bugs@lists.postgresql.org; Wed, 12 Jan 2022 11:16:44 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7bcQ-00072t-A0 for pgsql-bugs@lists.postgresql.org; Wed, 12 Jan 2022 11:16:44 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 037A93201D70; Wed, 12 Jan 2022 06:16:39 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 12 Jan 2022 06:16:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=j4is58iXwHIXG865lITUWYjNFJKZGybiV9wm6pAEd Ek=; b=Y5KcyUSYra/ItCKCqSksoG+n13xQ/tdZw26pNegNm/dt53UGL+K004hp+ anejSQBmEM6e3W6fd+4pixFt3jl0dJLNNUBfWgIESsxa4WO/WGEP18gP1ZZeuB8b ZyB9ZytqybGkVzx2bmU8HOlq8Vps3209FHCElL/abtVRX2VNXMoP2NpIXvmgGrC+ f2AKznpoopTSzRiQO354SDIL9rxlAYTDKKhEh1sVEB2SjL2ApmNM69LjS7zd/xXQ Y3wACAk9ONS4gFufZ9Lo7R0zFPPdJKl84ltE2iYfIx72y7bdm2B7pZzEYOsB0cAP 5q5fMagDS0Fcgk+rYECCJGQrzJWJQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtdduucetufdoteggodetrfdotffvucfrrh hofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurh epkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomheprfgvthgvrhcugfhi shgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvghrphhrih hsvggusgdrtghomheqnecuggftrfgrthhtvghrnheplefgteefiedtleelgeegjeevhfeu teefvddtjeehveeuieefgedvhfeuleduteeunecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhht vghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 12 Jan 2022 06:16:38 -0500 (EST) Message-ID: Date: Wed, 12 Jan 2022 12:16:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: Postgres HA and Pglogical Content-Language: en-US To: Padmakumar Kadayaprth , PostgreSQL mailing lists References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 >