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 1symjq-0029H4-E6 for pgsql-admin@arkaria.postgresql.org; Thu, 10 Oct 2024 06:33:31 +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 1symjp-00CPry-KB for pgsql-admin@arkaria.postgresql.org; Thu, 10 Oct 2024 06:33:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1symjp-00CPqu-7O for pgsql-admin@lists.postgresql.org; Thu, 10 Oct 2024 06:33:29 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1symjm-000Ic0-D2 for pgsql-admin@lists.postgresql.org; Thu, 10 Oct 2024 06:33:28 +0000 Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a9982159d98so91172066b.1 for ; Wed, 09 Oct 2024 23:33:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=cybertec.at; t=1728542006; x=1729146806; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=4J0M/pJcJamUBHDbaZBnLiYumeIHNNaTXAvv5Ce7bh4=; b=nCPd6LtlZ6onOTxO9UTFprgKZwHtEz+PUVOSGu9Z38JnFQZMfsyQgUoQT6b+64G3vj mGjzi818Ox0DPqDE7EmHuNXQ+Zdmbw/et/JSOD6LQIIbdEGYaBV7bPgeN23gZwcFdjba z12NYFpTL2Epk6rn+7/t1lpxc8Zas9Ncat7uM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728542006; x=1729146806; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=4J0M/pJcJamUBHDbaZBnLiYumeIHNNaTXAvv5Ce7bh4=; b=s3Wp6YzzI+9G6xEqIGvDh0zdIp4n24cOhGdC4Rgbwc/BfwgGGhwTvLCCuxLc4naV91 bB5n2y773d/Qs8tqcV8Gc9p8A3NOIooqOtcrd9JrXcw2RbeChqpno8t53TCuNdfEuJCT 7OQLv5PPlL5n0rCuF2g7mYTumdnl5cer7wRJtV3KQn3SqmWZjVB9Vy0BQKw1/ve5n+v4 jBG0a/Hp6H9Xb355gwpBeKbvN9/B/frfDn7GUxm+RZEbDHrma3qFiO3UfRuZvHxVm8PL v/WHd5P5W0/bgcGZQVh4dPgx8as2UG12Q58r3v0SGgKTxctN5YgeXLuvapdfMJAh78LI RRTg== X-Gm-Message-State: AOJu0YytGOh5Y0L8F5X+YNUs12Z45q0X7W0s7cVsLCPlsnay7HXksgR7 0c6jRA6CSa4Te8vxg3PxU/Nz+1Ai5ISJXbde6tjrvnZab7WDzmXVnGLf4JYRg84= X-Google-Smtp-Source: AGHT+IGWjB6paC15x3fUr3TiihqaJfAjeeBPrcQwL1aHRQnPYzSjprlhHPSMHsZAnz+BQ1zRJpVWwg== X-Received: by 2002:a17:907:f75a:b0:a99:4987:8878 with SMTP id a640c23a62f3a-a998d1a2576mr453018766b.15.1728542006019; Wed, 09 Oct 2024 23:33:26 -0700 (PDT) Received: from dynamic-pd01.res.v6.highway.a1.net ([2001:871:5e:3ea:8b4d:f178:5ba3:758c]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a99a80bfbd5sm40408166b.102.2024.10.09.23.33.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Oct 2024 23:33:25 -0700 (PDT) Message-ID: <35e0128148572d2dadfbda0fe748dcac988d3722.camel@cybertec.at> Subject: Re: RHEL certified repo provided PostgreSQL Major Version Upgrade. From: Laurenz Albe To: Sameer Malve , Tom Lane Cc: "pgsql-admin@lists.postgresql.org" , Sameer Malve Date: Thu, 10 Oct 2024 08:33:25 +0200 In-Reply-To: References: <1910788.1728395149@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.4 (3.52.4-1.fc40) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2024-10-10 at 11:52 +0530, Sameer Malve wrote: > I have few questions. >=20 > 1. As I have observed, the PostgreSQL upgrade package has only the lower > major version binaries. So what if I want to upgrade from PG 13 to PG = 16? That works just the same. > 2. If upgrade fails then what are the rollback steps. Do you=C2=A0know if= it is documented somewhere?=C2=A0 If you didn't use the --link option of pg_upgrade, you can simply fall back= to the old cluster. If you used --link, you will have to restore your backup (or promote a stan= dby server that you prepared for this eventuality). See the pg_upgrade documentation. Yours, Laurenz Albe