public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: In-order pg_dump (or in-order COPY TO)
Date: Wed, 27 Aug 2025 10:31:24 -0400
Message-ID: <CANzqJaAYu6ff9KqrEqU==JMNErGqszC__SZuZp1Wnwz=nFkXWQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Wed, Aug 27, 2025 at 10:16 AM Tom Lane <[email protected]> wrote:
> Dimitrios Apostolou <[email protected]> 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!
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: In-order pg_dump (or in-order COPY TO)
In-Reply-To: <CANzqJaAYu6ff9KqrEqU==JMNErGqszC__SZuZp1Wnwz=nFkXWQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox