@@ -337,14 +337,16 @@ PostgreSQL documentation
337
337
but to abort the dump.
338
338
</para>
339
339
<para>
340
- For a consistent backup, the database server needs to support synchronized snapshots,
341
- a feature that was introduced in <productname>PostgreSQL</productname> 9.2. With this
342
- feature, database clients can ensure they see the same data set even though they use
343
- different connections. <command>pg_dump -j</command> uses multiple database
344
- connections; it connects to the database once with the master process and
345
- once again for each worker job. Without the synchronized snapshot feature, the
346
- different worker jobs wouldn't be guaranteed to see the same data in each connection,
347
- which could lead to an inconsistent backup.
340
+ For a consistent backup, the database server needs to support
341
+ synchronized snapshots, a feature that was introduced in
342
+ <productname>PostgreSQL</productname> 9.2 for primary servers and 10
343
+ for standbys. With this feature, database clients can ensure they see
344
+ the same data set even though they use different connections.
345
+ <command>pg_dump -j</command> uses multiple database connections; it
346
+ connects to the database once with the master process and once again
347
+ for each worker job. Without the synchronized snapshot feature, the
348
+ different worker jobs wouldn't be guaranteed to see the same data in
349
+ each connection, which could lead to an inconsistent backup.
348
350
</para>
349
351
<para>
350
352
If you want to run a parallel dump of a pre-9.2 server, you need to make sure that the
0 commit comments