Message-ID: <0dd498c38c94ab2090634f55fb034eed7a1fc57b.camel@cybertec.at>
Subject: Re: Improve documentation for pg_upgrade, standbys and rsync
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-docs@lists.postgresql.org, pgsql-hackers@lists.postgresql.org
Date: Wed, 19 May 2021 18:53:49 +0200
In-Reply-To: <20210519143135.GI20766@tamriel.snowman.net>
References: <22f129004bb66cd91e1dfd3345a9787f5039f3ae.camel@cybertec.at>
	 <20210519143135.GI20766@tamriel.snowman.net>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/0dd498c38c94ab2090634f55fb034eed7a1fc57b.camel%40cybertec.at>
Precedence: bulk

On Wed, 2021-05-19 at 10:31 -0400, Stephen Frost wrote:
> * Laurenz Albe (laurenz.albe@cybertec.at) wrote:
> > I revently tried to upgrade a standby following the documentation,
> > but I found it hard to understand, [...]
>
> Haven't had a chance to look at this in depth but improving things here
> would be good.
> 
> An additional thing that we should really be mentioning is to tell
> people to go in and TRUNCATE all of their UNLOGGED tables before going
> through this process, otherwise the rsync will end up spending a bunch
> of time copying the files for UNLOGGED relations which you really don't
> want.

Thanks for the feedback and the suggestion.
CCing -hackers so that I can add it to the commitfest.

Yours,
Laurenz Albe