X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 40AA8D1B16A for ; Sun, 18 Jul 2004 14:24:06 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 08441-03 for ; Sun, 18 Jul 2004 17:24:02 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id 78B15D1B275 for ; Sun, 18 Jul 2004 14:23:59 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 5799011; Sun, 18 Jul 2004 10:25:08 -0700 Content-Type: text/plain; charset="iso-8859-15" From: Josh Berkus Organization: Aglio Database Solutions To: =?iso-8859-15?q?Herv=E9=20Piedvache?= , pgsql-performance@postgresql.org Subject: Re: Insert are going slower ... Date: Sun, 18 Jul 2004 10:23:21 -0700 User-Agent: KMail/1.4.3 Cc: Shridhar Daithankar , =?iso-8859-15?q?Herv=E9=20Piedvache?= References: <200407131850.52095.herve@elma.fr> <200407151109.16466.josh@agliodbs.com> <200407161317.02515.herve@elma.fr> In-Reply-To: <200407161317.02515.herve@elma.fr> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200407181023.22004.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/117 X-Sequence-Number: 7508 Herve' > Hum ... it's only for speed aspect ... I was using postgresql with this > option since 7.01 ... and for me fsync=on was so slow ... > Is it really no time consuming for the system to bring it ON now with > v7.4.3 ?? Well, I wouldn't do it until you've figured out the current performance problem. The issue with having fsync=off is that, if someone yanks the power cord on your server, there is a significant chance that you will have to restore the database from backup becuase it will be corrupted. But clearly you've been living with that risk for some time. It *is* true that there is significantly less performance difference between 7.4 with fsync off and on than there was between 7.1 with fsync off and on. But there is still a difference. In 7.0 and 7.1 (I think), when you turned fsync off it turned WAL off completely, resulting in a substantial difference in disk activity. Now, it just stops checkpointing WAL but WAL is still recording -- meaning that disk activity decreases some but not a lot. The difference is more noticable the more vulnerable to contention your disk system is. The other reason not to think of fsync=off as a permanent performance tweak is that we're likely to remove the option sometime in the next 2 versions, since an increasing number of features depend on WAL behavior, and the option is largely a legacy of the 7.0 days, when WAL was sometimes buggy and needed to be turned off to get the database to start. -- Josh Berkus Aglio Database Solutions San Francisco