Re: Improve documentation for pg_upgrade, standbys and rsync - Mailing list pgsql-docs

From Stephen Frost
Subject Re: Improve documentation for pg_upgrade, standbys and rsync
Date
Msg-id 20210519143135.GI20766@tamriel.snowman.net
Whole thread Raw
In response to Improve documentation for pg_upgrade, standbys and rsync  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Improve documentation for pg_upgrade, standbys and rsync  (Laurenz Albe <laurenz.albe@cybertec.at>)
Re: Improve documentation for pg_upgrade, standbys and rsync  (Laurenz Albe <laurenz.albe@cybertec.at>)
Re: Improve documentation for pg_upgrade, standbys and rsync  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-docs
Greetings,

* Laurenz Albe (laurenz.albe@cybertec.at) wrote:
> I revently tried to upgrade a standby following the documentation,
> but I found it hard to understand, and it took me several tries to
> get it right.  This is of course owing to my lack of expertise with
> rsync, but I think the documentation and examples could be clearer.
>
> I think it would be a good idea to recommend the --relative option
> of rsync.
>
> Here is a patch that does that, as well as update the versions in
> the code samples to something more recent.  Also, I think it makes
> sense to place the data directory in the sample in /var/lib/postgresql,
> which is similar to what many people will have in real life.

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,

Stephen

Attachment

pgsql-docs by date:

Previous
From: "tanghy.fnst@fujitsu.com"
Date:
Subject: RE: typo in doc for "Miscellaneous Coding Conventions"
Next
From: Andrew Dunstan
Date:
Subject: Re: Error building for 64-bit Windows (10)