diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 68 | ||||
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 48 | ||||
| -rw-r--r-- | doc/src/sgml/release-9.1.sgml | 7 |
3 files changed, 48 insertions, 75 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 8a6d7b7c5fd..bb5527c0624 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1507,8 +1507,9 @@ SET ENABLE_SEQSCAN TO OFF; <para> Specifies whether transaction commit will wait for WAL records to be written to disk before the command returns a <quote>success</> - indication to the client. The default, and safe, setting is - <literal>on</>. When <literal>off</>, there can be a delay between + indication to the client. Valid values are <literal>on</>, + <literal>local</>, and <literal>off</>. The default, and safe, value + is <literal>on</>. When <literal>off</>, there can be a delay between when success is reported to the client and when the transaction is really guaranteed to be safe against a server crash. (The maximum delay is three times <xref linkend="guc-wal-writer-delay">.) Unlike @@ -1523,6 +1524,19 @@ SET ENABLE_SEQSCAN TO OFF; discussion see <xref linkend="wal-async-commit">. </para> <para> + If <xref linkend="guc-synchronous-standby-names"> is set, this + parameter also controls whether or not transaction commit will wait + for the transaction's WAL records to be flushed to disk and replicated + to the standby server. The commit wait will last until a reply from + the current synchronous standby indicates it has written the commit + record of the transaction to durable storage. If synchronous + replication is in use, it will normally be sensible either to wait + both for WAL records to reach both the local and remote disks, or + to allow the transaction to commit asynchronously. However, the + special value <literal>local</> is available for transactions that + wish to wait for local flush to disk, but not synchronous replication. + </para> + <para> This parameter can be changed at any time; the behavior for any one transaction is determined by the setting in effect when it commits. It is therefore possible, and useful, to have some @@ -2057,39 +2071,6 @@ SET ENABLE_SEQSCAN TO OFF; </para> <variablelist> - <varlistentry id="guc-synchronous-replication" xreflabel="synchronous_replication"> - <term><varname>synchronous_replication</varname> (<type>boolean</type>)</term> - <indexterm> - <primary><varname>synchronous_replication</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Specifies whether transaction commit will wait for WAL records - to be replicated before the command returns a <quote>success</> - indication to the client. The default setting is <literal>off</>. - When <literal>on</>, there will be a delay while the client waits - for confirmation of successful replication. That delay will - increase depending upon the physical distance and network activity - between primary and standby. The commit wait will last until a - reply from the current synchronous standby indicates it has written - the commit record of the transaction to durable storage. This - parameter has no effect if - <xref linkend="guc-synchronous-standby-names"> is empty or - <xref linkend="guc-max-wal-senders"> is zero. - </para> - <para> - This parameter can be changed at any time; the - behavior for any one transaction is determined by the setting in - effect when it commits. It is therefore possible, and useful, to have - some transactions replicate synchronously and others asynchronously. - For example, to make a single multistatement transaction commit - asynchronously when the default is synchronous replication, issue - <command>SET LOCAL synchronous_replication TO OFF</> within the - transaction. - </para> - </listitem> - </varlistentry> - <varlistentry id="guc-synchronous-standby-names" xreflabel="synchronous_standby_names"> <term><varname>synchronous_standby_names</varname> (<type>string</type>)</term> <indexterm> @@ -2098,7 +2079,7 @@ SET ENABLE_SEQSCAN TO OFF; <listitem> <para> Specifies a priority ordered list of standby names that can offer - synchronous replication. At any one time there will be just one + synchronous replication. At any one time there will be at most one synchronous standby that will wake sleeping users following commit. The synchronous standby will be the first named standby that is both currently connected and streaming in real-time to the standby @@ -2114,18 +2095,17 @@ SET ENABLE_SEQSCAN TO OFF; not enforced for uniqueness. In case of duplicates one of the standbys will be chosen to be the synchronous standby, though exactly which one is indeterminate. - </para> - <para> - No value is set by default. The special entry <literal>*</> matches any application_name, including the default application name of <literal>walreceiver</>. </para> <para> - If a standby is removed from the list of servers then it will stop - being the synchronous standby, allowing another to take its place. - If the list is empty, synchronous replication will not be - possible, whatever the setting of <varname>synchronous_replication</>. - Standbys may also be added to the list without restarting the server. + If no synchronous standby names are specified, then synchronous + replication is not enabled and transaction commit will never wait for + replication. This is the default configuration. Even when + synchronous replication is enabled, individual transactions can be + configured not to wait for replication by setting the + <xref linkend="guc-synchronous-commit"> parameter to + <literal>local</> or <literal>off</>. </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index f6308dd7849..6dbc6bcd721 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -929,19 +929,18 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' <title>Basic Configuration</title> <para> - All parameters have useful default values, so we can enable - synchronous replication easily just by setting this on the primary: - -<programlisting> -synchronous_replication = on -</programlisting> - - When <varname>synchronous_replication</> is set, a commit will wait - for confirmation that the standby has received the commit record, - even if that takes a very long time. - <varname>synchronous_replication</> can be set by individual + Once streaming replication has been configured, configuring synchronous + replication requires only one additional configuration step: + <xref linkend="guc-synchronous-standby-names"> must be set to + a non-empty value. <varname>synchronous_commit</> must also be set to + <literal>on</>, but since this is the default value, typically no change is + required. This configuration will cause each commit to wait for + confirmation that the standby has written the commit record to durable + storage, even if that takes a very long time. + <varname>synchronous_commit</> can be set by individual users, so can be configured in the configuration file, for particular - users or databases, or dynamically by applications. + users or databases, or dynamically by applications, in order to control + the durability guarantee on a per-transaction basis. </para> <para> @@ -959,17 +958,10 @@ synchronous_replication = on </para> <para> - Users will stop waiting if a fast shutdown is requested, though the - server does not fully shutdown until all outstanding WAL records are - transferred to standby servers. - </para> - - <para> - Note also that <varname>synchronous_commit</> is used when the user - specifies <varname>synchronous_replication</>, overriding even an - explicit setting of <varname>synchronous_commit</> to <literal>off</>. - This is because we must write WAL to disk on primary before we replicate - to ensure the standby never gets ahead of the primary. + 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> </sect3> @@ -1019,9 +1011,9 @@ synchronous_replication = on <title>Planning for High Availability</title> <para> - Commits made when synchronous_replication is set will wait until - the sync standby responds. The response may never occur if the last, - or only, standby should crash. + Commits made when <varname>synchronous_commit</> is set to <literal>on</> + will wait until the sync standby responds. The response may never occur + if the last, or only, standby should crash. </para> <para> @@ -1073,8 +1065,8 @@ synchronous_replication = on 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 - synchronous_replication = off, otherwise those requests will wait - forever for the standby to appear. + <varname>synchronous_commit</> = <literal>off</>, otherwise those + requests will wait forever for the standby to appear. </para> </sect3> diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml index 5671682b3f1..5152bb3fe40 100644 --- a/doc/src/sgml/release-9.1.sgml +++ b/doc/src/sgml/release-9.1.sgml @@ -651,14 +651,15 @@ </para> <para> + This allows the primary to wait for a standby to write the transaction + information to disk before acknowledging the commit. One standby at a time can take the role of the synchronous standby, as controlled by the <link linkend="guc-synchronous-standby-names"><varname>synchronous_standby_names</varname></link> setting. Synchronous replication can be enabled or disabled on a per-transaction basis using the - <link linkend="guc-synchronous-replication"><varname>synchronous_replication</></link> - setting. This allows the primary to wait for a standby to write the - transaction information to disk before acknowledging the commit. + <link linkend="guc-synchronous-commit"><varname>synchronous_commit</></link> + setting. </para> </listitem> |