diff options
| author | Magnus Hagander <magnus@hagander.net> | 2011-08-17 11:01:06 +0200 |
|---|---|---|
| committer | Magnus Hagander <magnus@hagander.net> | 2011-08-17 11:01:50 +0200 |
| commit | aee1df4de5006300cfb59b531933b1e0142a8735 (patch) | |
| tree | d77be9126f73f4db6419207b4dabf0cf68b501cc | |
| parent | 59dd4790e24b2fdffe85b8d3664a8374303cca24 (diff) | |
Adjust wording now that estimated size can increase
Per comment form Fujii Masao.
| -rw-r--r-- | doc/src/sgml/ref/pg_basebackup.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml index 4150f2a4088..94367b06148 100644 --- a/doc/src/sgml/ref/pg_basebackup.sgml +++ b/doc/src/sgml/ref/pg_basebackup.sgml @@ -229,8 +229,8 @@ PostgreSQL documentation the backup, this is only an approximation and may not end at exactly <literal>100%</literal>. In particular, when WAL log is included in the backup, the total amount of data cannot be estimated in advance, and - in this case the progress report will only count towards the total - amount of data without WAL. + in this case the estimated target size will increase once it passes the + total estimate without WAL. </para> <para> When this is enabled, the backup will start by enumerating the size of |