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 1oixgv-00019G-Jo for pgsql-admin@arkaria.postgresql.org; Thu, 13 Oct 2022 12:52:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oixgu-0000dX-Fa for pgsql-admin@arkaria.postgresql.org; Thu, 13 Oct 2022 12:52:00 +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 1oixgu-0000dO-4j for pgsql-admin@lists.postgresql.org; Thu, 13 Oct 2022 12:52:00 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oixgq-0005lx-SO for pgsql-admin@lists.postgresql.org; Thu, 13 Oct 2022 12:51:58 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id BE36AE5AD7; Thu, 13 Oct 2022 12:51:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at emo08-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo08-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSOC2UOIOalk; Thu, 13 Oct 2022 12:51:54 +0000 (UTC) Received: from smtpclient.apple (unknown [165.140.184.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 68974E5AB7; Thu, 13 Oct 2022 12:51:54 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: Postgresql community edition upgrade From: Scott Ribe In-Reply-To: Date: Thu, 13 Oct 2022 06:51:53 -0600 Cc: pgsql-admin Content-Transfer-Encoding: quoted-printable Message-Id: <3DEF677C-D70F-43F5-A912-4DA0C8C949D3@elevated-dev.com> References: <7ce8278e-f943-74d4-ca73-cbf9e422f784@jakobs.com> <9571D051-5B4F-45FB-A52B-9D84C601B7DC@elevated-dev.com> <183cdeb4338.2923.9bfe8bcc586ac955e423c0e3d5444448@pscs.co.uk> To: Ebin Jozer X-Mailer: Apple Mail (2.3696.120.41.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Oct 13, 2022, at 3:42 AM, Ebin Jozer wrote: >=20 > We have master and slave environment. So for upgrade we have upgrade = first in slave and then in master environment. Please confirm Depends on your HA requirements. Easiest: shut down primary and all db access, upgrade one, bring it back = up as primary, upgrade other and bring it back online as replica. Harder: use a replication scheme that works across versions = (publish/subscribe, pglogical, londiste, bucardo) so that you can bring = up a new replica on the new version, switch over to it with minimal = downtime (just enough to make sure changes from master have been = replicated), then turn the former primary into a new replica.=