Re: deduplicating backup of multiple pg_dump dumps - Mailing list pgsql-admin

From Laurenz Albe
Subject Re: deduplicating backup of multiple pg_dump dumps
Date
Msg-id 1517234620.2622.41.camel@cybertec.at
Whole thread Raw
In response to deduplicating backup of multiple pg_dump dumps  (Egor Duda <egor.duda@gmail.com>)
Responses Re: deduplicating backup of multiple pg_dump dumps  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Egor Duda wrote:
> I've recently tried to use borg backup (https://borgbackup.readthedocs.io/) to store multiple
> PostgreSQL database dumps, and encountered a problem. Due to nondeterministic nature of pg_dump it
> reorders data tables rows on each invocation, which breaks borg backup chunking and deduplication
> algorithm.
> 
> This means that each next dump in backup almost never reuses data from previous dumps, and so it's
> not possible to store multiple database dumps as efficiently as possible.
> 
> I wonder if there's any way to force pg_dump use some predictable ordering of data rows (for
> example, by primary key, where possible) to make dumps more uniform, similar to mysqldump
> --order-by-primary option?

There is no such option.

I think you would be better off with physical backups using "pg_basebackup" if you
want to deduplicate, at least if deduplication is on the block level.

Yours,
Laurenz Albe


pgsql-admin by date:

Previous
From: Egor Duda
Date:
Subject: deduplicating backup of multiple pg_dump dumps
Next
From: Tom Lane
Date:
Subject: Re: deduplicating backup of multiple pg_dump dumps