From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Fabio Pardi <f(dot)pardi(at)portavita(dot)eu> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) |
Date: | 2019-06-14 14:39:40 |
Message-ID: | 20190614143940.vux2quolie4s6luv@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
On Fri, Jun 14, 2019 at 03:12:29PM +0200, Fabio Pardi wrote:
> Hi Bruce,
>
>
> On 6/14/19 5:30 AM, Bruce Momjian wrote:
>
> >> 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.
> >
>
>
> Maybe I am missing something, but I am of the opinion that --size-only
> should not be used when syncing database content (and probably in many
> other use cases where content can change over time).
>
> The reason is that db allocates blocks, 8K by default regardless from
> the content.
>
> Using --size-only, tells rsync to only check the size of the blocks.
> That is: if the block is present on the destination, and is the same
> size as the origin, then skip.
The files are _exactly_ the same on primary and standby, so we don't
need to check anything. Frankly, it is really only doing hard linking
of the files.
--
Bruce Momjian <bruce(at)momjian(dot)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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-06-14 14:44:09 | Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) |
Previous Message | Fabio Pardi | 2019-06-14 13:12:29 | Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-06-14 14:44:09 | Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) |
Previous Message | Fabio Pardi | 2019-06-14 13:46:30 | wal_log_hints benchmarks |