Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) - Mailing list pgsql-performance

From Bruce Momjian
Subject Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)
Date
Msg-id 20190614033001.5jif725fxchtopg7@momjian.us
Whole thread Raw
In response to Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)  (Fabio Pardi <f.pardi@portavita.eu>)
Responses Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)  (Fabio Pardi <f.pardi@portavita.eu>)
List pgsql-performance
On Thu, May 23, 2019 at 01:31:01PM +0200, Fabio Pardi wrote:
> Hi Mariel,
> 
> 
> On 5/23/19 1:07 PM, Mariel Cherkassky wrote:
> > 
> > 
> > Hey,
> > 
> > I upgraded the primary, then I run the rsync command in the primary : 
> > rsync --archive --delete --hard-links --size-only --no-inc-recursive
> > /var/lib/pgsql/data /var/lib/pgsql/11/data/
> > secondary_ip:/var/lib/pgsql/data/
> 
> rsync needs only 2 arguments, not 3.
> 
> You are here passing /var/lib/pgsql/data /var/lib/pgsql/11/data/
> secondary_ip:/var/lib/pgsql/data/
> 
> and if you try to do that, you will end up copying the content of the
> first folder into the third.
> 
> Therefore your secondary database will contain what on the primary is in
> /var/lib/pgsql/data/ (guess, 9.6.0)
> 
> Also, I do not think it best practice (or perhaps not correct at all) to
> use '--size-only'

--size-only is correct, as far as I know.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-performance by date:

Previous
From: Ancoron Luciferis
Date:
Subject: Re: UUID v1 optimizations...
Next
From: Fabio Pardi
Date:
Subject: Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched)