From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Dimitrios Apostolou <jimis(at)gmx(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: In-order pg_dump (or in-order COPY TO) |
Date: | 2025-08-26 22:54:52 |
Message-ID: | daf47435-539f-4368-869c-dd19a341399b@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/26/25 12:43, Dimitrios Apostolou wrote:
> Hello list,
>
> I am storing dumps of a database (pg_dump custom format) in a de-
> duplicating backup server. Each dump is many terabytes in size, so
> deduplication is very important. And de-duplication itself is based on
> rolling checksums which is pretty flexible, it can compensate for blocks
> moving by some offset.
>
> Unfortunately after I did pg_restore to a new server, I notice that the
> dumps from the new server are not being de-duplicated, all blocks are
> considered new.
What are the pg_dump/pg_restore commands?
What are the Postgres versions involved?
Are they community versions of Postgres or something else?
What is the depduplication program?
> Thanks in advance,
> Dimitris
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitrios Apostolou | 2025-08-27 12:09:39 | Re: In-order pg_dump (or in-order COPY TO) |
Previous Message | Tom Lane | 2025-08-26 22:23:45 | Re: In-order pg_dump (or in-order COPY TO) |