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 1jkmdJ-0006ug-E2
	for pgsql-admin@arkaria.postgresql.org; Mon, 15 Jun 2020 10:46:30 +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 1jkmdG-0000Ox-8J
	for pgsql-admin@arkaria.postgresql.org; Mon, 15 Jun 2020 10:46:26 +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 <vas@sibptus.ru>)
	id 1jkmdF-0000Op-UU
	for pgsql-admin@lists.postgresql.org; Mon, 15 Jun 2020 10:46:26 +0000
Received: from admin.sibptus.ru ([2001:19f0:5001:21dc::10])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <vas@sibptus.ru>)
	id 1jkmdC-0000lQ-Fo
	for pgsql-admin@lists.postgresql.org; Mon, 15 Jun 2020 10:46:24 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru;
	 s=20181118; h=Message-ID:Subject:To:From:Date:In-Reply-To;
	bh=oDYeggUHE1z7A53M1SYQoStPI8FAbV/QPo1ZrBx89To=; b=c5YZdkrETpWBIW29Od9G6kQDeU
	MeAEhJ41+BajGCKewzRrHNj+XW4/zQZIvv30uJLJ7859i2sl7Zhs+ZVrSS/2VpaGs/VMo07CtjNWW
	cT4MA7m++aT92oG7D7Ay8V8L5LP4amYeGccdXT+UOvka/v+SmFrlJy2qRTAMYjt3nvyM=;
Received: from vas by admin.sibptus.ru with local (Exim 4.94 (FreeBSD))
	(envelope-from <vas@sibptus.ru>)
	id 1jkmd9-000PKF-PF
	for pgsql-admin@lists.postgresql.org; Mon, 15 Jun 2020 17:46:19 +0700
Date: Mon, 15 Jun 2020 17:46:19 +0700
From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: Upgrade streaming replication and log-shipping standby servers
Message-ID: <20200615104619.GA97072@admin.sibptus.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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>
Precedence: bulk

Dear Colleagues,

When upgrading to a new major version, pg_upgrade documentation
https://www.postgresql.org/docs/current/pgupgrade.html#PGUPGRADE-STEP-REPLICAS
states that pg_upgrade can be used on a master server. After upgrading
the PostgreSQL version on standbys, however, one must either pull the
data from scratch with pg_basebackup, or run rsync from master to
standby.

Is running pg_upgrade on replicas not supported and why?

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