diff --git a/doc/src/sgml/high-availability.sgml 
b/doc/src/sgml/high-availability.sgml
new file mode 100644
index ed34dac..c5f3ff9
*** a/doc/src/sgml/high-availability.sgml
--- b/doc/src/sgml/high-availability.sgml
*************** primary_conninfo = 'host=192.168.1.50 po
*** 1022,1028 ****
  
     <para>
      Users will stop waiting if a fast shutdown is requested.  However, as
!     when using asynchronous replication, the server will does not fully
      shutdown until all outstanding WAL records are transferred to the 
currently
      connected standby servers.
     </para>
--- 1022,1028 ----
  
     <para>
      Users will stop waiting if a fast shutdown is requested.  However, as
!     when using asynchronous replication, the server will not fully
      shutdown until all outstanding WAL records are transferred to the 
currently
      connected standby servers.
     </para>
*************** primary_conninfo = 'host=192.168.1.50 po
*** 1126,1132 ****
  
     <para>
      If you need to re-create a standby server while transactions are
!     waiting, make sure that the commands to run pg_start_backup() and
      pg_stop_backup() are run in a session with
      <varname>synchronous_commit</> = <literal>off</>, otherwise those
      requests will wait forever for the standby to appear.
--- 1126,1132 ----
  
     <para>
      If you need to re-create a standby server while transactions are
!     waiting, make sure that the commands pg_start_backup() and
      pg_stop_backup() are run in a session with
      <varname>synchronous_commit</> = <literal>off</>, otherwise those
      requests will wait forever for the standby to appear.


Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/

Attachment: signature.asc
Description: Digital signature

Reply via email to