Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 1E5176329A7 for ; Mon, 11 Jan 2010 15:45:57 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 33774-06 for ; Mon, 11 Jan 2010 19:45:46 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f220.google.com (mail-fx0-f220.google.com [209.85.220.220]) by mail.postgresql.org (Postfix) with ESMTP id 5A340632483 for ; Mon, 11 Jan 2010 15:45:46 -0400 (AST) Received: by fxm20 with SMTP id 20so21043926fxm.35 for ; Mon, 11 Jan 2010 11:45:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JCWsoj3uQpZyL3I0RdS3cGEz/78NvX5vqKXVLaHt+Do=; b=kZ6WTZo9G8sesYhA/CMri7vIlNSkWN44FUTj5G7bAou9WQw+Hr8DpkfEPkKvRNElf6 V8ckbGrh8n1J1RNUNqPdSkK4xjf6zavlm0ObAdzxIgpfzOeYwAWIxlnz2bv8+bUi+qhW YW3UdwPzjXizCWZYCiSa0w/1iTARioCPuafM8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GinrhsNyo2GYASyFQBOhwj4KOts6x3jKA1DEMEEr2KaTNw21s7kRds50JCjRLILQf/ hHkU3PMAg6az7O17Srk1pLRNIuDtnOwjJrZ8A2eehakhiDdipAa6ClgYQV+BEcNG8T9K y6inNgWFgY1LFD/g5WKtsoKP/5Nt7s2d2/Nlg= MIME-Version: 1.0 Received: by 10.216.85.137 with SMTP id u9mr2944348wee.214.1263239144138; Mon, 11 Jan 2010 11:45:44 -0800 (PST) In-Reply-To: <61039b861001111134ja2ab11cr1c83e34b24377f4d@mail.gmail.com> References: <4B4B177B020000250002E194@gw.wicourts.gov> <61039b861001111134ja2ab11cr1c83e34b24377f4d@mail.gmail.com> Date: Mon, 11 Jan 2010 12:45:44 -0700 Message-ID: Subject: Re: performance config help From: Scott Marlowe To: Bob Dusek Cc: Kevin Grittner , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.589 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FH_DATE_PAST_20XX=3.188 X-Spam-Level: X-Archive-Number: 201001/213 X-Sequence-Number: 37093 On Mon, Jan 11, 2010 at 12:34 PM, Bob Dusek wrote: > Yeah :)=A0 We haven't run into much trouble.=A0 But, we cut our teeth doi= ng > performance analysis of our app using PG 7.4.=A0 And, people on this list= seem > to be adamantly against this config these days.=A0 Is this safer in older > versions of PG?=A0 Or, are the risks the same? It's always been unsafe. Just that 7.4 was so slow that sometimes you didn't really get to choose. > We have some asynchronous communications processes that communicate > permanent db changes to an enterprise-level data warehouse.=A0 And, we ca= n > recover that data back down to the server if the server goes belly-up.=A0= If > something does go belly up, we really only lose the bit of data that hasn= 't > been communicated yet.=A0 It's true, that this data is important.=A0 Howe= ver, > it's also true that it's very costly to guarantee this that very small > amount of data isn't lost.=A0 And, practically speaking (for our purposes= ) it > seems that the data's not worth the cost. I have slave dbs running on four 7200RPM SATA drives with fsync off. They only get updated from the master db so if they go boom, I just recreate their node. There's times fsync off is ok, you just have to know that that db is now considered "disposable". However, I'd suggest doing some benchmarking to PROVE that you're seeing an improvement from fsync being off. If there's no improvement, then you might as well leave it on and save yourself some headache later on when the machine gets powered off suddenly etc.