Re: In-order pg_dump (or in-order COPY TO)

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: In-order pg_dump (or in-order COPY TO)
Date: 2025-08-27 14:31:24
Message-ID: CANzqJaAYu6ff9KqrEqU==JMNErGqszC__SZuZp1Wnwz=nFkXWQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Aug 27, 2025 at 10:16 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Dimitrios Apostolou <jimis(at)gmx(dot)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!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2025-08-27 14:42:57 Re: In-order pg_dump (or in-order COPY TO)
Previous Message Tom Lane 2025-08-27 14:16:33 Re: In-order pg_dump (or in-order COPY TO)