Feedback-ID: i76984098:Fastmail
Message-ID: <daf47435-539f-4368-869c-dd19a341399b@aklaver.com>
Date: Tue, 26 Aug 2025 15:54:52 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: In-order pg_dump (or in-order COPY TO)
To: Dimitrios Apostolou <jimis@gmx.net>, pgsql-general@lists.postgresql.org
References: <s0491qrn-343s-0757-8sn5-120rr8610qqq@tzk.arg>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <s0491qrn-343s-0757-8sn5-120rr8610qqq@tzk.arg>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/daf47435-539f-4368-869c-dd19a341399b%40aklaver.com>
Precedence: bulk

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.klaver@aklaver.com