Re: In-order pg_dump (or in-order COPY TO)
От | Tom Lane |
---|---|
Тема | Re: In-order pg_dump (or in-order COPY TO) |
Дата | |
Msg-id | 1389082.1756304193@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: In-order pg_dump (or in-order COPY TO) (Dimitrios Apostolou <jimis@gmx.net>) |
Ответы |
Re: In-order pg_dump (or in-order COPY TO)
|
Список | pgsql-general |
Dimitrios Apostolou <jimis@gmx.net> writes: > Dump is from PostgreSQL 16, it's pg_dump writing to stdout: > pg_dump -v --format=custom --compress=none --no-toast-compression --serializable-deferrable db_name | borg create ... Don't use --format=custom (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
В списке pgsql-general по дате отправления: