mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +03:00
Remove pg_dump's --no-synchronized-snapshots switch.
Server versions for which there was a plausible reason to use this switch are all out of support now. Leaving it around would accomplish little except to let careless DBAs shoot themselves in the foot. Discussion: https://postgr.es/m/556122.1639520324@sss.pgh.pa.us
This commit is contained in:
@@ -387,7 +387,7 @@ PostgreSQL documentation
|
||||
but to abort the dump.
|
||||
</para>
|
||||
<para>
|
||||
For a consistent backup, the database server needs to support
|
||||
To perform a parallel dump, the database server needs to support
|
||||
synchronized snapshots, a feature that was introduced in
|
||||
<productname>PostgreSQL</productname> 9.2 for primary servers and 10
|
||||
for standbys. With this feature, database clients can ensure they see
|
||||
@@ -931,18 +931,6 @@ PostgreSQL documentation
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>--no-synchronized-snapshots</option></term>
|
||||
<listitem>
|
||||
<para>
|
||||
This option allows running <command>pg_dump -j</command> against a
|
||||
pre-v10 standby server, at the cost of possibly producing an
|
||||
inconsistent dump. See the documentation of the <option>-j</option>
|
||||
parameter for more details.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>--no-tablespaces</option></term>
|
||||
<listitem>
|
||||
|
Reference in New Issue
Block a user