Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vGfZM-003mvq-A8 for pgsql-general@arkaria.postgresql.org; Wed, 05 Nov 2025 15:37:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vGfZJ-003ESb-OD for pgsql-general@arkaria.postgresql.org; Wed, 05 Nov 2025 15:37:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vGfZI-003ESS-P5 for pgsql-general@lists.postgresql.org; Wed, 05 Nov 2025 15:37:04 +0000 Received: from fout-b3-smtp.messagingengine.com ([202.12.124.146]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vGfZF-005bbf-2B for pgsql-general@lists.postgresql.org; Wed, 05 Nov 2025 15:37:02 +0000 Received: from phl-compute-11.internal (phl-compute-11.internal [10.202.2.51]) by mailfout.stl.internal (Postfix) with ESMTP id 1D5101D001A9; Wed, 5 Nov 2025 10:37:00 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-11.internal (MEProxy); Wed, 05 Nov 2025 10:37:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1762357019; x=1762443419; bh=DIblJ8qhO9AgYHaUtp5fHMirpqHqCjLJKoIkijsxick=; b= WUFAudoAedhrwPMzPsT9qaa8dWlqk1DkhTNO1D75S6/0AO3T5yHPLDNIpp90kn+Y Rv6F4HzZWq+4Br284ehcsCN483/GELna33koUZ6SbmK7hOo9xo9SwsNqZixoTNzL /oZlODuACWMw4e6N1v4UbSUKJSPnvu/pcmTewV/UoIIEm8cotcR8P2LQZ9KPlTG8 h5jW3bmBrosj9bHUOQbzF4aLigZhLJM4DhRAk4RxYMGLKEp8jZFBzPLpTw8GS3Lk 6z9DGt26cemXrr2+DZXS6u/t7Y4nPUtB78zb0OFD8GiNlB2+G6sDCARF4iD9PVku mUs9Frk0UgWZ0CEOCw/2zA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1762357019; x= 1762443419; bh=DIblJ8qhO9AgYHaUtp5fHMirpqHqCjLJKoIkijsxick=; b=P FCT8J4NydKpoxc7RngJtUBR9+a0GjJo5ONXJaSzPxPPfpqytmAqVyrctSD0NuVrl UxWdwqONV2usAYavtH6Z2groKjTY7juPvo8fyGTEWWQ5tz1HKvp4yqj4nEatB9/5 kTGm7XUrQdwW2Lom5xNhDJv/zjXuzQr4jsL0oCT5PYDvOoPQwA+1Fy3KG9kvQWt/ Ju9SppuvscXCBZeAv4UmwLaVhWH2UV78bdRhVfbp/D7/K7RYzv09WyMAaI4pxvz0 vT7d6BfKxkHpff1kGkM+s7GgV2HU+Ym8z8J2kTIR2Maxvd7hazZ2UtynjiaOLR2m u9ZKt65hRhtFYJ/OAwvAA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddukeegvdekucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpeetughrihgr nhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh eqnecuggftrfgrthhtvghrnhephfeviefhveelffeftdehudekveefhfeftdegieefveet fffgfeehtdfftedutedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgs pghrtghpthhtohephedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepkhhrihhshh hnrgdrphhguggsrgesghhmrghilhdrtghomhdprhgtphhtthhopehhthgrmhhfihgushes ghhmrghilhdrtghomhdprhgtphhtthhopehfohhlrghrthgvsehpvghophhlvggtrghllh drtghomhdprhgtphhtthhopegthhhrihhsodhgohhoghhlvgesqhifihhrgidrtghomhdp rhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlihhsthhsrdhpohhsthhgrhgvsh hqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Nov 2025 10:36:58 -0500 (EST) Message-ID: <942b979a-c5e8-40e7-bdec-0234a0e5a010@aklaver.com> Date: Wed, 5 Nov 2025 07:36:58 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Index corruption issue after migration from RHEL 7 to RHEL 9 (PostgreSQL 11 streaming replication) To: Bala M , Greg Sabino Mullane , Francisco Olarte Cc: chris+google@qwirx.com, pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/4/25 22:27, Bala M wrote: > Thank you all for your suggestions, > > Thanks for your quick response and for sharing the details. > After reviewing the options, the logical replication approach seems to > be the most feasible one with minimal downtime. > > However, we currently have 7 streaming replication setups running from > production, with a total database size of around 15 TB. Out of this, > there are about 10 large tables ranging from 1 TB (max) to 50 GB (min) > each, along with approximately 150+ sequences. > > Could you please confirm if there are any successful case studies or > benchmarks available for a similar setup? Since you have given minimal information in this post, I doubt there is really a way to compare to other situations. Collect the details you provided earlier in the thread for those folks getting to it just now. That would be: 1) Postgres versions on both ends 2) OS and versions on both ends. 3) Network distance between 'machines'. 4) The logical replication settings. > Additionally, please share any recommended parameter tuning or best > practices for handling logical replication at this scale. Since you have already started is that not already to late for this? > > Current server configuration: > > CPU: 144 cores > > RAM: 512 GB > > > Thanks & Regards > Krishna. > -- Adrian Klaver adrian.klaver@aklaver.com