From b4b8efbd3826ac0af2d1c2e7c40fcf80a4bfba45 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:03 +0200 Subject: Adding upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/warm-standby.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src/sgml/html/warm-standby.html') diff --git a/doc/src/sgml/html/warm-standby.html b/doc/src/sgml/html/warm-standby.html index 88a2d47..7ac58c1 100644 --- a/doc/src/sgml/html/warm-standby.html +++ b/doc/src/sgml/html/warm-standby.html @@ -1,5 +1,5 @@ -27.2. Log-Shipping Standby Servers

27.2. Log-Shipping Standby Servers

+27.2. Log-Shipping Standby Servers

27.2. Log-Shipping Standby Servers

Continuous archiving can be used to create a high availability (HA) cluster configuration with one or more standby servers ready to take over operations if the @@ -103,7 +103,7 @@ later disconnected, the standby goes back to step 1 and tries to restore the file from the archive again. This loop of retries from the archive, pg_wal, and via streaming replication goes on until the server - is stopped or failover is triggered by a trigger file. + is stopped or is promoted.

Standby mode is exited and the server switches to normal operation when pg_ctl promote is run, @@ -654,4 +654,4 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' are found in the archive, but not if streaming replication is enabled. When a server is not in recovery mode, there is no difference between on and always modes. -

\ No newline at end of file +

\ No newline at end of file -- cgit v1.2.3