X-Git-Url: https://git.gag.com/?p=debian%2Famanda;a=blobdiff_plain;f=man%2Fxml-source%2Fampgsql.8.xml;h=21fc0b79b7186319960e489c921fa834ef283bc8;hp=cea1fc5643aee4ea091988ba4cdb1329472dfff9;hb=b116e9366c7b2ea2c2eb53b0a13df4090e176235;hpb=fd48f3e498442f0cbff5f3606c7c403d0566150e
diff --git a/man/xml-source/ampgsql.8.xml b/man/xml-source/ampgsql.8.xml
index cea1fc5..21fc0b7 100644
--- a/man/xml-source/ampgsql.8.xml
+++ b/man/xml-source/ampgsql.8.xml
@@ -174,6 +174,37 @@ will be searched.
+RECOVERY
+
+Read the postgres documentation carefully before attempting a recovery.
+This section is only a rough guide to the process.
+
+The data recovered from a postgres backup consists of a data tarball and
+one or more archive tarballs. The data contains the state of the database
+at the time the full backup was performed, and the archive tarballs contain
+postgres WAL files that must be re-run to generate a consistent
+state.
+
+Ensure that the database server is shut down, and move the existing data
+directory aside. Untar the data tarball over this directory, and verify
+that ownership and permissions are correct. Untar all of the archive
+tarballs into a single directory - the archive directory. Create a
+recovery.conf in the data directory, owned by the
+proper user and with proper permissions. Add a
+restore_command to it, e.g.,
+
+
+restore_command = 'cp /path/to/archive_dir/%f "%p"'
+
+
+Start the database server, and examine the logs to track the process of
+the recovery. When the recovery is complete, the server will transition
+into a running state, and will move the recovery.conf
+file aside so that it will not attempt a recovery on the next
+invocation.
+
+
+
,
,