public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Ron Johnson <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: In-order pg_dump (or in-order COPY TO)
Date: Tue, 26 Aug 2025 18:23:45 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaCxNP9TjC9WnhaF3F_FKBmL7UXKRiQzoV5nnDS4vmbnxg@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CANzqJaCxNP9TjC9WnhaF3F_FKBmL7UXKRiQzoV5nnDS4vmbnxg@mail.gmail.com>

Ron Johnson <[email protected]> writes:
> On Tue, Aug 26, 2025 at 6:08 PM Tom Lane <[email protected]> wrote:
>> I'd expect pg_dump/pg_restore to preserve the physical row ordering,
>> simply because it doesn't do anything that would change that.

> But the rolling checksums are against a pg_dump file, not a pg_basebackup
> file.

Oh, that wasn't clear to me.

> What probably changed are table OIDs.  Would that change the ordering of
> COPY data in post-restore dump files?

It would not change the order of data within any one table.  There are
corner cases in which different OID assignments can cause pg_dump to
emit database objects in a different order, see this recent thread:

https://www.postgresql.org/message-id/flat/20250707192654.9e.nmisch%40google.com

			regards, tom lane

view thread (22+ 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], [email protected]
  Subject: Re: In-order pg_dump (or in-order COPY TO)
  In-Reply-To: <[email protected]>

* 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