Force a checkpoint before committing a CREATE DATABASE command. This

should fix the recent reports of "index is not a btree" failures,
as well as preventing a more obscure race condition involving changes
to a template database just after copying it with CREATE DATABASE.

1 files changed, 13 insertions, 1 deletions

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 099483766e0..d61fe997e6f 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.54.4.5 2005/04/19 01:40:02 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.54.4.6 2005/06/25 22:47:49 tgl Exp $
 -->
 <chapter id="backup">
  <title>Backup and Restore</title>
@@ -1145,6 +1145,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