X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5FFD3D1B51A for ; Mon, 29 Sep 2003 21:42:13 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 80981-04 for ; Mon, 29 Sep 2003 18:41:46 -0300 (ADT) Received: from wight.ymogen.net (unknown [217.27.240.153]) by svr1.postgresql.org (Postfix) with SMTP id 912F1D1B4FF for ; Mon, 29 Sep 2003 18:41:43 -0300 (ADT) Received: (qmail 1005 invoked from network); 29 Sep 2003 21:41:40 -0000 Received: from dsl-217-155-239-51.zen.co.uk (HELO finisterre) (217.155.239.51) by wight.ymogen.net with SMTP; 29 Sep 2003 21:41:40 -0000 From: "Matt Clark" To: "Palle Girgensohn" , , Subject: Re: advice on raid controller Date: Mon, 29 Sep 2003 22:41:39 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <39060000.1064871114@palle.girgensohn.se> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/378 X-Sequence-Number: 3744 Not in general. Besides, with a write-back cache an fsync() is very nearly 'free', as the controller will report the write as completed as soon as it's written to cache. I keep meaning to benchmark the difference, but I only have the facility on a production box, so caution gets the better of me every time :-) AFAIK the fsync calls are used to guarantee the _ordering_ of writes to permanent storage (i.e. fsync() is called before doing something, rather than after doing something. So PG can be sure that before it does B, A has definitely been written to disk). But I could well be wrong. And there could well be strategies exploitable with the knowledge that a write-back cache exists that aren't currently implemented - though intuitively I doubt it. M > -----Original Message----- > From: Palle Girgensohn [mailto:girgen@pingpong.net] > Sent: 29 September 2003 22:32 > To: Matt Clark; rj@last.fm; pgsql-performance@postgresql.org > Subject: Re: [PERFORM] advice on raid controller > > > Stupid question, perhaps, but would a battery-backed cache make > it safe to > set fsync=false in postgresql.conf? > > /Palle > > --On söndag, september 28, 2003 13.07.57 +0100 Matt Clark > > wrote: > > > As others have mentioned, you really ought to get > battery-backed cache if > > you're doing any volume of writes. The ability to do safe write-back > > caching makes an *insane* difference to write performance. > > > > >