diff options
| author | Robert Haas <rhaas@postgresql.org> | 2012-04-14 10:53:22 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2012-04-14 10:53:22 -0400 |
| commit | ea6a2d8d47b9368f50fb7f4cca206895e6127a0a (patch) | |
| tree | f32fd95dfea0eeea8f9a2a4d03a863b8d1c026b0 /doc/src | |
| parent | 4a2d7ad76f5f275ef2d6a57e1a61d5bf756349e8 (diff) | |
| download | postgresql-ea6a2d8d47b9368f50fb7f4cca206895e6127a0a.tar.gz postgresql-ea6a2d8d47b9368f50fb7f4cca206895e6127a0a.zip | |
Rename synchronous_commit='write' to 'remote_write'.
Fujii Masao, per discussion on pgsql-hackers
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 361ad7b99a5..cffca4e46c9 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1626,7 +1626,7 @@ 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. Valid values are <literal>on</>, <literal>write</>, + indication to the client. Valid values are <literal>on</>, <literal>remote_write</>, <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 @@ -1646,7 +1646,7 @@ SET ENABLE_SEQSCAN TO OFF; 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. When <literal>write</>, the commit wait will + to the standby server. When <literal>remote_write</>, the commit wait will last until a reply from the current synchronous standby indicates it has received the commit record of the transaction to memory. Normally this causes no data loss at the time of failover. However, diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 64e4319bf6d..c268bfb8d3f 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1011,7 +1011,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' </para> <para> - Setting <varname>synchronous_commit</> to <literal>write</> will + Setting <varname>synchronous_commit</> to <literal>remote_write</> will cause each commit to wait for confirmation that the standby has received the commit record to memory. This provides a lower level of durability than <literal>on</> does. However, it's a practically useful setting @@ -1075,7 +1075,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' <para> Commits made when <varname>synchronous_commit</> is set to <literal>on</> - or <literal>write</> will wait until the synchronous standby responds. The response + or <literal>remote_write</> will wait until the synchronous standby responds. The response may never occur if the last, or only, standby should crash. </para> |