From 4fb0ae0dc43c0085c355f16dcff0c39bab7b39b6 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 2 Feb 2008 23:29:12 +0000 Subject: [PATCH] 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. --- doc/src/sgml/config.sgml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 28762592c3..9191a775b9 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1343,9 +1343,7 @@ SET ENABLE_SEQSCAN TO OFF; In many situations, turning off for noncritical transactions can provide much of the potential performance benefit of turning off fsync, without - the attendant risks of data corruption. It can even be turned - off in a single multi-statement transaction using SET - LOCAL synchronous_commit TO OFF;. + the attendant risks of data corruption. @@ -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 SET + LOCAL synchronous_commit TO OFF within the transaction. -- 2.39.5