summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/pg_dump.sgml10
-rw-r--r--doc/src/sgml/ref/pg_dumpall.sgml4
2 files changed, 0 insertions, 14 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 9d6708431cf..374bca66a0a 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -834,16 +834,6 @@ PostgreSQL documentation
and the two systems have different definitions of the collation used
to sort the partitioning column.
</para>
-
- <para>
- It is best not to use parallelism when restoring from an archive made
- with this option, because <application>pg_restore</application> will
- not know exactly which partition(s) a given archive data item will
- load data into. This could result in inefficiency due to lock
- conflicts between parallel jobs, or perhaps even restore failures due
- to foreign key constraints being set up before all the relevant data
- is loaded.
- </para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml
index 30ef97dd4a2..e57f119bad6 100644
--- a/doc/src/sgml/ref/pg_dumpall.sgml
+++ b/doc/src/sgml/ref/pg_dumpall.sgml
@@ -358,10 +358,6 @@ PostgreSQL documentation
and the two systems have different definitions of the collation used
to sort the partitioning column.
</para>
-
- <!-- Currently, we don't need pg_dump's warning about parallelism here,
- since parallel restore from a pg_dumpall script is impossible.
- -->
</listitem>
</varlistentry>