diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2004-08-29 21:08:48 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2004-08-29 21:08:48 +0000 |
| commit | 50742aed68b7a3a8d1a0c8ef8d970c97fc74dd9b (patch) | |
| tree | c60891419eb5cb4e2c73296f973d91bba13f9e03 /doc/src | |
| parent | ee66401f3176e32c884ce98c09c8383cfa453dbc (diff) | |
| download | postgresql-50742aed68b7a3a8d1a0c8ef8d970c97fc74dd9b.tar.gz postgresql-50742aed68b7a3a8d1a0c8ef8d970c97fc74dd9b.zip | |
Add WAL logging for CREATE/DROP DATABASE and CREATE/DROP TABLESPACE.
Fix TablespaceCreateDbspace() to be able to create a dummy directory
in place of a dropped tablespace's symlink. This eliminates the open
problem of a PANIC during WAL replay when a replayed action attempts
to touch a file in a since-deleted tablespace. It also makes for a
significant improvement in the usability of PITR replay.
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/backup.sgml | 14 |
1 files changed, 3 insertions, 11 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 7a3c4f73ff9..af06249203a 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.46 2004/08/08 04:34:43 tgl Exp $ +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.47 2004/08/29 21:08:47 tgl Exp $ --> <chapter id="backup"> <title>Backup and Restore</title> @@ -902,19 +902,11 @@ restore_command = 'cp /mnt/server/archivedir/%f %p' <para> At this writing, there are several limitations of the on-line backup - technique. These will probably be fixed in future releases. + technique. These will probably be fixed in future releases: <itemizedlist> <listitem> <para> - The effects of <command>CREATE DATABASE</>, <command>DROP DATABASE</>, - <command>CREATE TABLESPACE</>, and <command>DROP TABLESPACE</> are - not fully reflected in the WAL log. It is recommended that you take - a new base backup after performing one of these operations. - </para> - </listitem> - <listitem> - <para> Operations on non-btree indexes (hash, R-tree, and GiST indexes) are not presently WAL-logged, so replay will not update these index types. The recommended workaround, if you use any non-btree indexes, is to @@ -932,7 +924,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p' since we may need to fix partially-written disk pages. It is not necessary to store so many page copies for PITR operations, however. An area for future development is to compress archived WAL data by - removing unnecesssary page copies. + removing unnecessary page copies. </para> </sect2> </sect1> |