Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiiEM-0002Vv-Gl for pgsql-admin@arkaria.postgresql.org; Wed, 12 Oct 2022 20:21:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oiiEK-0001Db-1v for pgsql-admin@arkaria.postgresql.org; Wed, 12 Oct 2022 20:21:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiiEJ-00019S-C2 for pgsql-admin@lists.postgresql.org; Wed, 12 Oct 2022 20:21:27 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oiiEC-00067h-Co for pgsql-admin@lists.postgresql.org; Wed, 12 Oct 2022 20:21:26 +0000 Received: by mail-ej1-x634.google.com with SMTP id fy4so3915911ejc.5 for ; Wed, 12 Oct 2022 13:21:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=4NwAbH3bMm7NcfAB5b7VxJzh4QaLnm+ga3zOcdXz5Tk=; b=nu9qOxpD0g39KMk060/jE0R8fnuq9ewIQ4balRKYwOemPkIZ3hSWA4yzJTqBH5l41z +WwN6PeCuMzis3DYD6demkcB6eA3Nt38KiMZFyYgj8UXip07j93Wdh4y39IxuMLFKdgt KnZHu0gxLBdVYlMH+o0Y7s66ly8AgEzDN4nKxdguKTmb1Za8p2wUbs8J/6Wz4Kfq/fXx n+kErIEXEwuEkUYZruRV5FmDX4HJ31uOm9nSoAUTQZMY3RABpE92W0TsTZuYLrAkqOgy xk7tZgZ+h8YWlJCXzZA33cdnFwlTrXdALnOVdD6kUonxwpAdcdBfB2wgYtefao+C3pGm c5gA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent: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=4NwAbH3bMm7NcfAB5b7VxJzh4QaLnm+ga3zOcdXz5Tk=; b=0n5//CNfHz8DtFXnJP7gqxURSIhAPs/5Z4BVm8Cq+A4rIyEvGodHJlxGKD1PflQw7K xer/nfHeVrkW5J8Af4s8NpZijCU2NCZrj882p70aTC0fr5I3ybyiaOvWcHVa44zVLecw c4sehkr50/A78P9zCqXt4ajO5Xe6EOooaR0PzGVrfGmSnSV3lX9f7P6AUb89+Kef9EDG l1lYW3kweAhXXYiqpBQmj3PFAB1ALrfy5aEvyTGKu2n2obOD+dX6TC8Bo81oFox2R0Cp vUg1+g8FCtaORgw90ocf+YBq/fEAddj9iDKk8Qix+rsFBIBqe/U+fTSiKmNrJWXggDqG Sbjg== X-Gm-Message-State: ACrzQf1dajFdzhKMPRER65KML92U7n2stvHVXYJeBDxTn84xrlHlI3Gf RHixpJM1owuq9sU/6pDcys5Fu0v81zCm5Q== X-Google-Smtp-Source: AMsMyM4I0BdvY3jr5J4mnJa4eNSEWi0n3N7ZtQmrIm/d1NG2cowjo8TolDIFR9wchVwz6hk/DmVw7w== X-Received: by 2002:a17:907:2ced:b0:78d:ece6:7cad with SMTP id hz13-20020a1709072ced00b0078dece67cadmr5294993ejc.136.1665606078719; Wed, 12 Oct 2022 13:21:18 -0700 (PDT) Received: from localhost.localdomain (178-190-171-155.adsl.highway.telekom.at. [178.190.171.155]) by smtp.gmail.com with ESMTPSA id v1-20020a1709067d8100b0078d957e65b6sm1827590ejo.23.2022.10.12.13.21.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 12 Oct 2022 13:21:18 -0700 (PDT) Message-ID: <4a1080b09b3cef27cd29dab046a4702498497512.camel@cybertec.at> Subject: Re: Postgresql community edition upgrade From: Laurenz Albe To: Ebin Jozer , Holger Jakobs Cc: pgsql-admin@lists.postgresql.org Date: Wed, 12 Oct 2022 22:21:17 +0200 In-Reply-To: References: <7ce8278e-f943-74d4-ca73-cbf9e422f784@jakobs.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2022-10-12 at 22:48 +0530, Ebin Jozer wrote: > What would be the rollback step in case the upgrade failed while using pg_upgrade?? If you don't use --link, the old cluster will still be there and can be used. If you use --link, restore your backup. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com