diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/backup.sgml | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index ba55eb634ae..01cdae83d69 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.68 2005/06/21 20:45:43 tgl Exp $ +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.69 2005/06/25 22:47:28 tgl Exp $ --> <chapter id="backup"> <title>Backup and Restore</title> @@ -1121,6 +1121,18 @@ restore_command = 'copy /mnt/server/archivedir/%f "%p"' # Windows <listitem> <para> + If a <command>CREATE DATABASE</> command is executed while a base + backup is being taken, and then the template database that the + <command>CREATE DATABASE</> copied is modified while the base backup + is still in progress, it is possible that recovery will cause those + modifications to be propagated into the created database as well. + This is of course undesirable. To avoid this risk, it is best not to + modify any template databases while taking a base backup. + </para> + </listitem> + + <listitem> + <para> <command>CREATE TABLESPACE</> commands are WAL-logged with the literal absolute path, and will therefore be replayed as tablespace creations with the same absolute path. This might be undesirable if the log is |