From a79122b06194927d2b79465f335b94f2b4472816 Mon Sep 17 00:00:00 2001 From: Simon Riggs Date: Fri, 23 Jun 2017 18:16:00 +0100 Subject: [PATCH] Minor corrections to high availability docs Startup process is displayed in pg_stat_activity, noted by Yugo Nagata. Transactions can be resolved at end of recovery. Author: Yugo Nagata, with addition by me --- doc/src/sgml/high-availability.sgml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 72eb073621..e41df791b7 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -2203,12 +2203,12 @@ LOG: database system is ready to accept read only connections pg_cancel_backend() and pg_terminate_backend() will work on user backends, but not the Startup process, which performs - recovery. pg_stat_activity does not show an - entry for the Startup process, nor do recovering transactions show - as active. As a result, pg_prepared_xacts - is always empty during recovery. If you wish to resolve in-doubt - prepared transactions, view pg_prepared_xacts on the - primary and issue commands to resolve transactions there. + recovery. pg_stat_activity does not show + recovering transactions as active. As a result, + pg_prepared_xacts is always empty during + recovery. If you wish to resolve in-doubt prepared transactions, view + pg_prepared_xacts on the primary and issue commands to + resolve transactions there or resolve them after the end of recovery.