public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jeff Janes <[email protected]>
To: Thorsten Schöning <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: How to get a more RSYNC compatible output of pg_dump?
Date: Wed, 18 May 2022 23:46:37 -0400
Message-ID: <CAMkU=1xmXSp-enz-EhLi0jL0-NJPFNxx3CEx7UJOh=EAxdLSig@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

>
> Though, with the large dumps it seems to me that with every slight
> change in the actual data the entire dump gets downloaded again. I'm
> already using uncompressed dumps in the hope that the output is more
> stable and RSYNC better able to recognize unchanged parts. But I guess
> that most changes in the dumped data simply result in all subsequent
> data being that misplaced compared to what RSYNC reads against, that
> it's like downloading the whole file again in the end.
>

For me the rsync differential algorithm on dump files just works with no
special preparations.  I think you need to investigate this from the rsync
side, not PostgreSQL.  For example, if you change a dump file just by
adding or deleting one character near the beginning, how does rsync respond
to that?

Cheers,

Jeff

view thread (8+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: How to get a more RSYNC compatible output of pg_dump?
  In-Reply-To: <CAMkU=1xmXSp-enz-EhLi0jL0-NJPFNxx3CEx7UJOh=EAxdLSig@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox