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 1tIFCH-00D9vA-Ka for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 22:47:17 +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 1tIFBH-004Mf2-3r for pgsql-general@arkaria.postgresql.org; Mon, 02 Dec 2024 22:46:16 +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 1tIFBG-004Met-Oh for pgsql-general@lists.postgresql.org; Mon, 02 Dec 2024 22:46:15 +0000 Received: from fout-b3-smtp.messagingengine.com ([202.12.124.146]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tIFBF-000ixD-4F for pgsql-general@postgresql.org; Mon, 02 Dec 2024 22:46:14 +0000 Received: from phl-compute-01.internal (phl-compute-01.phl.internal [10.202.2.41]) by mailfout.stl.internal (Postfix) with ESMTP id C41411140216; Mon, 2 Dec 2024 17:46:11 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-01.internal (MEProxy); Mon, 02 Dec 2024 17:46:11 -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=1733179571; x=1733265971; bh=cPCEOat8GMuVkMWqtlmQYJM580xP/3jXQ99CUbOvPgg=; b= msWIsURoYhmi+wfFsnqAU6w3DES7BUeU15BhVGT6GrbIZFgDmqMMkM+PbAg+XS/1 eZ3/29o/7MvSMcjuraFRb/1QJh25N7Sr36C2bIqGEZKsYw4d+fX9P7aWzyoFlqAu RWX3VTAGwn8/ToRIaCX/K5Zaur7941LteuSQ3dlJEnUrx23XA9iFdRzhT9R1lcFJ 8O2uul1Ru4NBxuofIRjFMIdAS0vNxJVIK6e8cI1FfX7UEdWZtOOzS8unoPRdS2fs Bbof8RkGAg6FpV4f/Q0r3mYNB9/IGdrQPIZL2HRFbPfK8dJ5jaD0RmfxAXUcShUd K6tsZSqywCZ6GxmO+TT0jQ== 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=1733179571; x=1733265971; bh=c PCEOat8GMuVkMWqtlmQYJM580xP/3jXQ99CUbOvPgg=; b=KWpHPRufxFU9itEbK DbE1Msi58/TgflnYmzDt0A48lLEWfgm57daoaAbXBtppSYNMP+UraSNNV++ga5OU iD9lMvMX/qMn1oQhvm+Skvn6F7Eejq8qySS9qQXLXYSBMVjunlL5Fc0M9iv8vG6Y +eP5iIGaWzSAlDLOzob7EY4cMpP0NdBA+wncKNrKjSCgG2ktUa9Mal3JqGJIzaPy JhQp1/NZahJPqqZAX0CRostGrpsaB4uXoZ2qNNIjlJfmrCqUS9bycoFEz7KSR9Sv /uoZV9gLQU1vl56gjyHD+cx9ad5/yWYdjHdm2bk41OkXzjlCWrmex02V24JJoFui MWJqg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddriedtgddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuf fvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcu oegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtth gvrhhnpeelgeevkeekkeeuiefgtdevieeluefhfedufeetkeejffekjeeujeehgeehgeek tdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhes rghklhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouh htpdhrtghpthhtoheprhhonhhljhhohhhnshhonhhjrhesghhmrghilhdrtghomhdprhgt phhtthhopehpghhsqhhlqdhgvghnvghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 2 Dec 2024 17:46:10 -0500 (EST) Message-ID: <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> Date: Mon, 2 Dec 2024 14:46:10 -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> 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 14:31, Ron Johnson wrote: > On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum > > wrote: > > Team > Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to > ver 15.X > > Env = EC2 based Community PostgreSQL Ver 13.16.2 > > we will be performing upgrade of our EC2 server too along with new OS. > > Need help in vetting my steps for Postgres DB upgrade from Ver 13.X > to ver 15.X > *ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2* > - ensure to capture all the pre.req meant for ver 15.10 are being met. > - shutdown db. > - take offline full backup (PG_DATA folder alone)  using OS command > > *Proposed-new EC2 server (with new Operating System version along > Postgres Ver 15.10 Binaries)* > - install postgres 15.10 binaries > - ensure to DISABLE auto startup and shutdown of postgres 15.10 > -  Restore offline full backup (PG_DATA folder alone) using OS command > -  start performing pg_upgrade step to upgrade postgres from ver > 13.16.2 to 15.10 > > please guide me, if i have missed any steps in the abovesaid process > > To start new DB features, planning to rollout out the following > feature's alone > a) TLE extension for password compliance > b) parallelize vacuum jobs to utilize -j option > > > To migrate from one server to another while upgrading, one must use > pg_dump/pg_restore OR Logical Replication. Really? Then this: https://www.postgresql.org/docs/current/pgupgrade.html must be random nose. > > -- > Death to , and butter sauce. > Don't boil me, I'm still alive. > lobster! -- Adrian Klaver adrian.klaver@aklaver.com