mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-27 08:39:28 +08:00
Move example of turning off synchronous_commit to a more logical place,
to wit in the description of that variable rather than some other one.
This commit is contained in:
parent
6f906905b1
commit
19c40492f0
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.163 2008/01/30 18:35:55 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.164 2008/02/02 23:29:12 tgl Exp $ -->
|
||||
|
||||
<chapter Id="runtime-config">
|
||||
<title>Server Configuration</title>
|
||||
@ -1343,9 +1343,7 @@ SET ENABLE_SEQSCAN TO OFF;
|
||||
In many situations, turning off <xref linkend="guc-synchronous-commit">
|
||||
for noncritical transactions can provide much of the potential
|
||||
performance benefit of turning off <varname>fsync</varname>, without
|
||||
the attendant risks of data corruption. It can even be turned
|
||||
off in a single multi-statement transaction using <command>SET
|
||||
LOCAL synchronous_commit TO OFF;</>.
|
||||
the attendant risks of data corruption.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@ -1385,6 +1383,9 @@ SET ENABLE_SEQSCAN TO OFF;
|
||||
one transaction is determined by the setting in effect when it
|
||||
commits. It is therefore possible, and useful, to have some
|
||||
transactions commit synchronously and others asynchronously.
|
||||
For example, to make a single multi-statement transaction commit
|
||||
asynchronously when the default is the opposite, issue <command>SET
|
||||
LOCAL synchronous_commit TO OFF</> within the transaction.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Loading…
Reference in New Issue
Block a user