From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: jcarson@fastmail.com, PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: request clarification on pg_restore documentation
Date: Fri, 27 Oct 2023 18:53:00 -0400
Message-ID: <1618733.1698447180@sss.pgh.pa.us> (raw)
In-Reply-To: <ZTw6wv8rkkC8IMk0@momjian.us>
References: <166446181317.661.16517798061228916974@wrigleys.postgresql.org>
<Yz7l/8HSP7rBB6vO@momjian.us>
<ZTw6wv8rkkC8IMk0@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> Does anyone have a suggestion on how to handle this issue?
It might be that the later decision to change the representation
of sequence dumps would make it possible to undo 4317e0246c
and go back to having --schema-only/--data-only be true aliases
for --section. But it'd take some research and probably end up
causing some behavioral changes (eg. trigger handling as you note).
Much the same research would be needed if you just wanted to
document the current state of affairs more clearly.
The real issue here is that --schema-only/--data-only do a few
things that are not within --section's remit, such as trigger
adjustments. Do we want to cause --section to have those effects
too? I dunno. Do we want to give up those extra behaviors?
Almost certainly not.
Either way, I'm not personally planning to put effort into that
anytime soon.
regards, tom lane
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: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, pgsql-hackers@postgresql.org
Subject: Re: request clarification on pg_restore documentation
In-Reply-To: <1618733.1698447180@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox