On Wed, 21 Jun 2017 19:08:35 +0530 Kuntal Ghosh <kuntalghosh.2...@gmail.com> wrote:
> On Wed, Jun 21, 2017 at 6:05 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote: > > > > Attached is a patch for the documentation fix. > > > Please attach the patch as well. :-) I'm sorry, I forgot it. I attahed this. > > > -- > Thanks & Regards, > Kuntal Ghosh > EnterpriseDB: http://www.enterprisedb.com > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers -- Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 72eb073..1188f07 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 <function>pg_cancel_backend()</> and <function>pg_terminate_backend()</> will work on user backends, but not the Startup process, which performs - recovery. <structname>pg_stat_activity</structname> does not show an - entry for the Startup process, nor do recovering transactions show - as active. As a result, <structname>pg_prepared_xacts</structname> - is always empty during recovery. If you wish to resolve in-doubt - prepared transactions, view <literal>pg_prepared_xacts</> on the - primary and issue commands to resolve transactions there. + recovery. <structname>pg_stat_activity</structname> does not show + recovering transactions as active. As a result, + <structname>pg_prepared_xacts</structname> is always empty during + recovery. If you wish to resolve in-doubt prepared transactions, view + <literal>pg_prepared_xacts</> on the primary and issue commands to + resolve transactions there. </para> <para>
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers