Request a Demo
Home   >   mailing lists

Re: In-order pg_dump (or in-order COPY TO) - Mailing list pgsql-general

From Ron Johnson
Subject Re: In-order pg_dump (or in-order COPY TO)
Date
Msg-id CANzqJaAYu6ff9KqrEqU==JMNErGqszC__SZuZp1Wnwz=nFkXWQ@mail.gmail.com
Whole thread Raw
In response to Re: In-order pg_dump (or in-order COPY TO)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: In-order pg_dump (or in-order COPY TO)
List pgsql-general
Tree view
On Wed, Aug 27, 2025 at 10:16 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
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,

That's interesting.  Why?  (Since isn't it supposed to be Bad to rely on OIDs?)

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: In-order pg_dump (or in-order COPY TO)
Next
From: Tom Lane
Date:
Subject: Re: In-order pg_dump (or in-order COPY TO)