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.96) (envelope-from ) id 1wD8at-002dwO-0t for pgsql-general@arkaria.postgresql.org; Wed, 15 Apr 2026 22:20:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wD8as-002ac0-1w for pgsql-general@arkaria.postgresql.org; Wed, 15 Apr 2026 22:20:22 +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.96) (envelope-from ) id 1wD8Xb-002V4I-2Y for pgsql-general@lists.postgresql.org; Wed, 15 Apr 2026 22:17:00 +0000 Received: from fout-a1-smtp.messagingengine.com ([103.168.172.144]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wD8XY-00000001DVC-2wNC for pgsql-general@lists.postgresql.org; Wed, 15 Apr 2026 22:16:58 +0000 Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id F3957EC00C4; Wed, 15 Apr 2026 18:16:55 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-02.internal (MEProxy); Wed, 15 Apr 2026 18:16:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= 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=fm1; t=1776291415; x=1776377815; bh=HPU2frPqBR4OQSmDOGJ8eY0TmqS8owlplULjQLBVY1c=; b= wUP2CSXgvhCG+lnDJvLe2ymunS+y6HWtqNHiqhdmbSMiNay0I3O2soqjG6lOcTDH 5ndm10zJmWAzBgTMs8or2WDFZHvvQ3Riu+2qb7w1W89kmUPIrlNfLuJpb8/SPFW1 OiVJma0YpIUhM0KbBxUwwiOiUKdIQtMwC9Yley2Lz/L93DbUuAY+lXYlp+T70AeL Fc92cpd75WJ02hnLJev3xCDA4gpzk3CWwEj9ymV5Tu0Qq92mbRYL7CKQg/uhblJT acWtC8sIV1YRvrN7tQFjjgf0V+FPSQ+lkzZQEX5eke+Y4jSYz7sYgtINQTZH1HKe knnGCE4rTvlaisu7VxKQ0A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm2; t=1776291415; x=1776377815; bh=H PU2frPqBR4OQSmDOGJ8eY0TmqS8owlplULjQLBVY1c=; b=hl20kuTU1z80KPKSL wMVJGoSPOInRpTyPZNr15tBLBadwbcP5UInAjOyhaaZ7choRixawxWQEmyuzmSow pN7Heqrq10+1JwDu+qthYi/i8Kl27+QbrgOJnN0HlqnTSKqLaIh7xaWJLHMH9hFa 095vn2QJqbiy6itzuLivvapMr84mTUVes01x/ZWxLDLS7+j+qvqDw8BrIRoZx6w8 xK8ywxQarQ0tJJGYd757GE5IgmzkTEc7eVvTpNJKPG/Zbmi0yat8O5ba6KVJgkA8 kJ4zp7Io02pp3Sppwhw/iZjZICVDS9D9cwHIklCpVzVrCMxgTTmY/aHDuOwHxe1Y ggsrg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdeghedvkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughrihgrnhcu mfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomheqne cuggftrfgrthhtvghrnhepgfefudejvdevveffudefvdejvdejieffgfdtgedtieeluedu jeehjefhkeefgedtnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghdprhgvrg guthhhvgguohgtshdrihhonecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnh gspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepjhhithhu rdhsrghnughhuhesghhmrghilhdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvg hrrghlsehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 Apr 2026 18:16:55 -0400 (EDT) Message-ID: <0184afec-b63a-4f1a-bb79-dd915954b273@aklaver.com> Date: Wed, 15 Apr 2026 15:16:54 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: physical replication compatibilty To: Jatinder Singh Sandhu , 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: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/15/26 3:06 PM, Jatinder Singh Sandhu wrote: > Dear PostgreSQL Community, > I am currently planning a major version upgrade from PostgreSQL 16 to > PostgreSQL 17. I have three node patroni cluster. While I am aware that > logical replication is the standard approach for cross-version > migrations, I am curious about the feasibility of physical streaming > replication in this specific scenario. > Specifically, I would like to clarify: > > 1. Is physical streaming replication backward compatible between these > two major versions? > 2. Since many data files remain consistent between versions, is there > any supported method to leverage physical block-level replication to > minimize the initial data synchronization time before a cutover? > > I understand that WAL formats and system catalogs typically change > between major releases, but I wanted to confirm if there are any modern > workarounds or "late-binding" techniques available in the v17 ecosystem. > Thank you for your time and expertise. I think you are looking for: https://www.postgresql.org/docs/17/pgupgrade.html In particular this: 13. Upgrade streaming replication and log-shipping standby servers Whether that will play well with the Patroni cluster or not is not something I can comment on. It is covered below though: https://patroni.readthedocs.io/en/latest/existing_data.html#major-upgrade-of-postgresql-version > Best regards,