From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dimitrios Apostolou <jimis@gmx.net>
cc: Adrian Klaver <adrian.klaver@aklaver.com>,
        pgsql-general@lists.postgresql.org
Subject: Re: In-order pg_dump (or in-order COPY TO)
In-reply-to: <3541781s-75o7-26pp-46pp-qs54o4406192@tzk.arg>
References: <s0491qrn-343s-0757-8sn5-120rr8610qqq@tzk.arg> <daf47435-539f-4368-869c-dd19a341399b@aklaver.com> <3541781s-75o7-26pp-46pp-qs54o4406192@tzk.arg>
Comments: In-reply-to Dimitrios Apostolou <jimis@gmx.net>
	message dated "Wed, 27 Aug 2025 14:09:39 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1389081.1756304193.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Aug 2025 10:16:33 -0400
Message-ID: <1389082.1756304193@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1389082.1756304193%40sss.pgh.pa.us>
Precedence: bulk

Dimitrios Apostolou <jimis@gmx.net> writes:
> Dump is from PostgreSQL 16, it's pg_dump writing to stdout:

> pg_dump -v --format=3Dcustom --compress=3Dnone --no-toast-compression --=
serializable-deferrable db_name  |  borg create ...

Don't use --format=3Dcustom (and not -v either).  That causes pg_dump to
include the OIDs and pg_dump object IDs of all the tables and other
objects, which will all be different in a dump from the new server.
The actual data contents of the tables should be the same, but
apparently the differences in the entry headers are enough to
mislead borgbackup.

You might be well advised to manually examine the data you are
stuffing into borgbackup.  Right now we seem to be operating on
hypotheses, not facts, about what that looks like and how it's
different between your old and new server.

			regards, tom lane