rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Simon Riggs 2017-06-23 18:16:00 +01:00
parent b6159202c9
commit a79122b061
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/high-availability.sgml
View File

@ -2203,12 +2203,12 @@ LOG: database system is ready to accept read only connections
<function>pg_cancel_backend()</> <function>pg_cancel_backend()</>
and <function>pg_terminate_backend()</> will work on user backends, and <function>pg_terminate_backend()</> will work on user backends,
but not the Startup process, which performs but not the Startup process, which performs
recovery. <structname>pg_stat_activity</structname> does not show an recovery. <structname>pg_stat_activity</structname> does not show
entry for the Startup process, nor do recovering transactions show recovering transactions as active. As a result,
as active. As a result, <structname>pg_prepared_xacts</structname> <structname>pg_prepared_xacts</structname> is always empty during
is always empty during recovery. If you wish to resolve in-doubt recovery. If you wish to resolve in-doubt prepared transactions, view
prepared transactions, view <literal>pg_prepared_xacts</> on the <literal>pg_prepared_xacts</> on the primary and issue commands to
primary and issue commands to resolve transactions there. resolve transactions there or resolve them after the end of recovery.
</para> </para>
<para> <para>