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 1tILSq-00Dm2E-4D for pgsql-general@arkaria.postgresql.org; Tue, 03 Dec 2024 05:28:48 +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 1tILSl-00710W-Sj for pgsql-general@arkaria.postgresql.org; Tue, 03 Dec 2024 05:28:45 +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 1tILSk-00710O-J1 for pgsql-general@lists.postgresql.org; Tue, 03 Dec 2024 05:28:44 +0000 Received: from fout-a2-smtp.messagingengine.com ([103.168.172.145]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tILSi-000luP-N5 for pgsql-general@postgresql.org; Tue, 03 Dec 2024 05:28:42 +0000 Received: from phl-compute-11.internal (phl-compute-11.phl.internal [10.202.2.51]) by mailfout.phl.internal (Postfix) with ESMTP id 5A51B13801DE; Tue, 3 Dec 2024 00:28:38 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-11.internal (MEProxy); Tue, 03 Dec 2024 00:28:38 -0500 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=fm3; t=1733203718; x=1733290118; bh=P4v1Apk8NtqyHb5Su+XQIk3iOsXl2xtEdy9CuVW3r8M=; b= O5xCJ4CmFSb669eUfc0z2esKyPLIdZnot9S0qHvC5JU+sZH0rLElP/8I4aErrJPH 6p5PeYMYPwJVZ6mvIWYffazVr4curKi8GWcWQse3oE9WiKQaKNkFMRUIqQnBPEbN fS4IZyGD/sEFGWl5zT+eXPnr5PqSoa3iESszMQ4tkSTFHWNddT++Q/syb/ARC8+b 4xti0GwB0cxuYCNu7cke/lfqlsnH8r5u0HNVHf7umgnALj4va3X8zmFx132Bc7+U avXxqJKMoWTnfiJphqD/wgdA9xaJYnQ+8ci5OTlMRmjU5ayrxhSkjmcoKQI7lP0t dy89x4OwT3BlYFCKg5xCXg== 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=fm1; t=1733203718; x=1733290118; bh=P 4v1Apk8NtqyHb5Su+XQIk3iOsXl2xtEdy9CuVW3r8M=; b=GJX3xK7G4wdLKo8HU 2/Wc9NZXzrO07JDSYA9zP4iPpYuxsPfO9r+nG+BuAbMJ3aCZisYblLzj2TSGY9t3 lQXoHHjJnYI0OZT/Aerm1JXjun9LtJglBCu3zyRXxxOvILBAds7Ww0PsZHzswohF UM46/H2K+GRNoJ4ZtKpqjxlWhF6jR9oZ3bAyIdvYomMHxPBPb+YjSohB1kOHIvR5 20mqnlv5R0ABYtECPJeoEPTIM3yvdq7B9JL9nZgL70WbGsVz3WMBaN5+6AxdYqNG ByZu3YR3thl/U9xAPKRiWyoInsdqn7GVC+A7+I6GxMY0BY1g3BowrLsPiq3nxrr0 lRQkw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddriedugddtgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuf fvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcu oegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtth gvrhhnpeffleegieefgfevudehtdfhkeeutdffjeevgeffgeejvedthefgudeiteefheej heenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrug hrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtthhopedv pdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehrohhnlhhjohhhnhhsohhnjhhrse hgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgrlhesphhoshht ghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 3 Dec 2024 00:28:37 -0500 (EST) Message-ID: <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com> Date: Mon, 2 Dec 2024 21:28:36 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X To: Ron Johnson , pgsql-general References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.com> <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> 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 12/2/24 17:23, Ron Johnson wrote: > Adrian, > > OP is moving to a new VM when migrating to PG 15.  When was the > "cross-server" feature added to pg_upgrade? > Moving to a new VM was not the issue, my mistake was thinking the OS version was staying the same. Then: On old VM: "take offline full backup (PG_DATA folder alone) using OS command" On new VM: "Restore offline full backup (PG_DATA folder alone) using OS command" Followed by installing new Postgres version could be dealt with using pg_upgrade. Once I was corrected on what was actually going on then doing a dump/restore or logical replication became better choices. -- Adrian Klaver adrian.klaver@aklaver.com