From 6ba9b9102aade07fae0b7e8f10813a54d385b5a1 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 5 Feb 2010 23:53:22 +0000 Subject: [PATCH] Mention warm and now "hot" standby servers in the high availability docs. --- doc/src/sgml/high-availability.sgml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index a51b00b9e5..6591dae193 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1,4 +1,4 @@ - + High Availability, Load Balancing, and Replication @@ -135,21 +135,22 @@ protocol to make nodes agree on a serializable transactional order. - Warm Standby Using Point-In-Time Recovery (PITR) + Warm and Hot Standby Using Point-In-Time Recovery (PITR) - A warm standby server (see ) can - be kept current by reading a stream of write-ahead log (WAL) + Warm and hot standby servers can be kept current by reading a + stream of write-ahead log (WAL) records. If the main server fails, the warm standby contains almost all of the data of the main server, and can be quickly made the new master database server. This is asynchronous and can only be done for the entire database server. - A PITR warm standby server can be kept more up-to-date using the - streaming replication feature built into PostgreSQL 8.5 - onwards; see . + A PITR standby server can be kept more up-to-date using streaming + replication.; see . For + warm standby information, see , and + for hot standby, see . -- 2.11.0