public inbox for [email protected]
help / color / mirror / Atom feedFrom: Thomas Munro <[email protected]>
To: Pavel Stehule <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: Large files for relations
Date: Wed, 3 May 2023 17:36:42 +1200
Message-ID: <CA+hUKGLP81Hvjbtzfr9c0V50dF+2pB2pOwvQ4MsWdU8-pa_H7Q@mail.gmail.com> (raw)
In-Reply-To: <CA+hUKGJxtfM3hLrmjP910_nm3DFCFZaUzbHG5Rhw6FpdLwpc6A@mail.gmail.com>
References: <CA+hUKG+BGXwMbrvzXAjL8VMGf25y_ga_XnO741g10y0=m6dDiA@mail.gmail.com>
<CAFj8pRCMQXtOUhxnGLYLL+T-5HwfjWLKYVN_hxi2VcG_PDD_GA@mail.gmail.com>
<CA+hUKGJxtfM3hLrmjP910_nm3DFCFZaUzbHG5Rhw6FpdLwpc6A@mail.gmail.com>
On Wed, May 3, 2023 at 5:21 PM Thomas Munro <[email protected]> wrote:
> rsync --link-dest
I wonder if rsync will grow a mode that can use copy_file_range() to
share blocks with a reference file (= previous backup). Something
like --copy-range-dest. That'd work for large-file relations
(assuming a file system that has block sharing, like XFS and ZFS).
You wouldn't get the "mtime is enough, I don't even need to read the
bytes" optimisation, which I assume makes all database hackers feel a
bit queasy anyway, but you'd get the space savings via the usual
rolling checksum or a cheaper version that only looks for strong
checksum matches at the same offset, or whatever other tricks rsync
might have up its sleeve.
view thread (4+ 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]
Subject: Re: Large files for relations
In-Reply-To: <CA+hUKGLP81Hvjbtzfr9c0V50dF+2pB2pOwvQ4MsWdU8-pa_H7Q@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