"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Tuesday, March 31, 2026, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Hmm, I think we could be a bit more definite than that. What do you >> think of this advice: >> >> <para> >> When creating an archive (non-text) output file, it is advisable not to >> restrict the set of database objects dumped, but instead plan to apply >> any desired object filtering when reading the archive >> with <application>pg_restore</application>. This will preserve >> flexibility and possibly avoid problems at restore time; for details >> see the <xref linkend="app-pgrestore"/> documentation. However, >> omitting table data (<option>--no-data</option>) or large objects >> (<option>--no-large-objects</option>) does not have any surprising >> consequences. >> </para>
> I’m against including that final sentence. The rest seems ok but I’ > suggest going with an explicit mention that “—no-schema is risky” (or > otherwise omitting the entire section)
How about replacing that sentence with "In particular, dumping table data without the corresponding table definition (via --no-schema and related options) is not recommended."
