Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Clarification in pg10's pgupgrade.html step 10(upgrading standby servers) - Mailing list pgsql-hackers

From Andreas Joseph Krogh
Subject Re: [HACKERS] Clarification in pg10's pgupgrade.html step 10(upgrading standby servers)
Date
Msg-id VisenaEmail.93.79215f39c91fa09e.15e7ba0e358@tc7-visena
Whole thread Raw
In response to Re: [HACKERS] Clarification in pg10's pgupgrade.html step 10(upgrading standby servers)  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] Clarification in pg10's pgupgrade.html step 10(upgrading standby servers)
List pgsql-hackers
Tree view
På onsdag 13. september 2017 kl. 15:26:27, skrev Bruce Momjian <bruce@momjian.us>:
On Wed, Sep 13, 2017 at 01:35:17AM +0200, Andreas Joseph Krogh wrote:
[snip]
> I know I'm being a little nitty-gritty here, but if it helps me understand it
> might help others.

I have applied the attached patch to show examples of using rsync on
PGDATA and tablespaces, documented that rsync is only useful when in
link mode, and explained more clearly how rsync handles links.  You can
see the results here:

http://momjian.us/pgsql_docs/pgupgrade.html

Any more improvements?
 
Very nice!
 
For sake of completeness I think an example of running rsync when having pg_wal located outside the data directories would be helpful. Especially an example upgrading from 9.6 to 10 because of the name-change of pg_xlog -> pg_wal.

--
Andreas Joseph Krogh

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [HACKERS] OpenFile() Permissions Refactor
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] psql: new help related to variables are not tooreadable