diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/backup.sgml | 7 | ||||
| -rw-r--r-- | doc/src/sgml/ref/pg_basebackup.sgml | 7 |
2 files changed, 7 insertions, 7 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 5d2cf5e5c9d..8b79b8f82f7 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -814,12 +814,13 @@ SELECT pg_stop_backup(); <para> You can also use the <xref linkend="app-pgbasebackup"> tool to take - the backup, instead of manually copying the files. This tool will take - care of the <function>pg_start_backup()</>, copy and + the backup, instead of manually copying the files. This tool will do + the equivalent of <function>pg_start_backup()</>, copy and <function>pg_stop_backup()</> steps automatically, and transfers the backup over a regular <productname>PostgreSQL</productname> connection using the replication protocol, instead of requiring filesystem level - access. + access. pg_basebackup does not interfere with filesystem level backups + taken using <function>pg_start_backup()</>/<function>pg_stop_backup()</>. </para> <para> diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml index f4f78fbbfc5..7ec14dc887a 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -59,10 +59,9 @@ PostgreSQL documentation </para> <para> - Only one backup can be concurrently active in - <productname>PostgreSQL</productname>, meaning that only one instance of - <application>pg_basebackup</application> can run at the same time - against a single database cluster. + There can be multiple pg_basebackups running at the same time, but it is + better from a performance point of view to take only one backup, and copy + the the result. </para> </refsect1> |