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 <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1pdnT1-0003Ir-NX
	for pgsql-admin@arkaria.postgresql.org; Sun, 19 Mar 2023 07:28:36 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1pdnSy-0004bA-Vs
	for pgsql-admin@arkaria.postgresql.org; Sun, 19 Mar 2023 07:28:32 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <vas@sibptus.ru>)
	id 1pdnSy-0004ay-AX
	for pgsql-admin@lists.postgresql.org; Sun, 19 Mar 2023 07:28:32 +0000
Received: from admin.sibptus.ru ([2001:19f0:5001:21dc::10])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <vas@sibptus.ru>)
	id 1pdnSq-0007Zh-M5
	for pgsql-admin@lists.postgresql.org; Sun, 19 Mar 2023 07:28:31 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru;
	s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date;
	bh=ypChLg2X3LqqwnZUssEoCSEsEnRPD8obDTpPxqnSWQo=; b=IjS9n03izB5WfwKoFHlQt1mYGw
	D9wSSFwOB0YEI2BdNRnoZpJwHLLEUbGfE9NHCkYmP/QIdm0u5iB1kr7vaT0PTftjqH1mZQ7FqVI/k
	O0+f9uY+8qoDdFkqmD/IooIFNYay5b8u/olhWkVLicrncyXar+jSIO6e9o6OMQpL5lpI=;
Received: from vas by admin.sibptus.ru with local (Exim 4.95 (FreeBSD))
	(envelope-from <vas@sibptus.ru>)
	id 1pdnSn-000C15-BK
	for pgsql-admin@lists.postgresql.org;
	Sun, 19 Mar 2023 07:28:21 +0000
Date: Sun, 19 Mar 2023 07:28:21 +0000
From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Upgrading Patroni from 2.1.x to 3.0.1 ?
Message-ID: <ZBa5lR/NiB3K02K0@admin.sibptus.ru>
References: <ZAWsyLajuJpIDdz8@admin.sibptus.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZAWsyLajuJpIDdz8@admin.sibptus.ru>
X-PGP-Key: http://admin.sibptus.ru/~vas/
X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9  3532 0DA4 F259 9B5E C634
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/ZBa5lR/NiB3K02K0%40admin.sibptus.ru>
Precedence: bulk

Victor Sudakov wrote:
> 
> Did you encounter any problems upgrading Patroni from 2.1.x to 3.0.1 ?
> 
> What's the recommended procedure, did you stop all cluster members
> (the patroni service and PostgreSQL instances themselves) before this
> major version upgrade?

In case someone has the same question. The upgrade did not cause any
problems and 3.0.1 seems backward compatible with 2.1.x.

I just stopped tne Patroni service on a cluster node, upgraded Patroni
and started the node with a new version, with no problems encountered. 

I'm missing the cluster ID in the `patronictl list` output a bit.

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet