|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.163 2008/01/30 18:35:55 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.164 2008/02/02 23:29:12 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter Id="runtime-config"> |
4 | 4 | <title>Server Configuration</title> |
@@ -1343,9 +1343,7 @@ SET ENABLE_SEQSCAN TO OFF; |
1343 | 1343 | In many situations, turning off <xref linkend="guc-synchronous-commit"> |
1344 | 1344 | for noncritical transactions can provide much of the potential |
1345 | 1345 | performance benefit of turning off <varname>fsync</varname>, without |
1346 | | - the attendant risks of data corruption. It can even be turned |
1347 | | - off in a single multi-statement transaction using <command>SET |
1348 | | - LOCAL synchronous_commit TO OFF;</>. |
| 1346 | + the attendant risks of data corruption. |
1349 | 1347 | </para> |
1350 | 1348 |
|
1351 | 1349 | <para> |
@@ -1385,6 +1383,9 @@ SET ENABLE_SEQSCAN TO OFF; |
1385 | 1383 | one transaction is determined by the setting in effect when it |
1386 | 1384 | commits. It is therefore possible, and useful, to have some |
1387 | 1385 | transactions commit synchronously and others asynchronously. |
| 1386 | + For example, to make a single multi-statement transaction commit |
| 1387 | + asynchronously when the default is the opposite, issue <command>SET |
| 1388 | + LOCAL synchronous_commit TO OFF</> within the transaction. |
1388 | 1389 | </para> |
1389 | 1390 | </listitem> |
1390 | 1391 | </varlistentry> |
|