Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!weretis.net!feeder4.news.weretis.net!newsfeed.utanet.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail From: "Laurenz Albe" Newsgroups: comp.databases.postgresql References: <927ub6F3drU1@mid.individual.net> Subject: Re: synchronous_commit on Wiki Date: Tue, 3 May 2011 10:29:47 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6090 Organization: dienste.wien.at ISP Message-ID: <1304411410.99095@proxy.dienste.wien.at> X-Cache: nntpcache 2.3.3 (see http://www.nntpcache.org/) Lines: 19 NNTP-Posting-Host: 141.203.254.23 X-Trace: 1304411411 aconews.univie.ac.at 73248 141.203.254.23 X-Complaints-To: abuse@univie.ac.at Xref: x330-a1.tempe.blueboxinc.net comp.databases.postgresql:112 Thomas Guettler wrote: > on http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server > > {{{ > For situations where a small amount of data loss is acceptable in return for a large boost in how many updates you can > do to the database per second, consider switching to synchronous commit > }}} > > I am not a native english speaker, but I think this is wrong. I guess it should > be "... consider switching synchronous commit off". You are right. See http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT Yours, Laurenz Albe