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 4BD548B9D95 for ; Thu, 3 Feb 2005 13:57:03 +0000 (GMT) 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 32968-03 for ; Thu, 3 Feb 2005 13:56:51 +0000 (GMT) Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by svr1.postgresql.org (Postfix) with ESMTP id 447F68B9E4F for ; Thu, 3 Feb 2005 13:56:53 +0000 (GMT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-33.mail.demon.net with esmtp (Exim 4.42) id 1CwhTZ-0009yP-AV; Thu, 03 Feb 2005 13:56:53 +0000 Received: from [192.168.1.17] (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 291CE158FE; Thu, 3 Feb 2005 13:56:52 +0000 (GMT) Message-ID: <42022DA2.3040000@archonet.com> Date: Thu, 03 Feb 2005 13:56:50 +0000 From: Richard Huxton User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Din Adrian Cc: 'Postgresql Performance' Subject: Re: Tunning postgresql on linux (fedora core 3) References: <420202D0.7070602@archonet.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.068 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200502/65 X-Sequence-Number: 10394 Please CC the mailing list as well as replying to me, so that others can help too. Din Adrian wrote: > yes I have read this as well ... > > One question about this option: > fsync = true / false > a) I have Raid and UPS - it is safe to turn this off ... (' But be > very aware that any unexpected database shutdown will force you to > restore the database from your last backup.' - from my last backup if > the server goes down ??? why ? just at 'any unexpected database > shutdown' ? ....!!!!!!!!!!!) Because fsync=true flushes transaction details to disk (the Write Ahead Log). That way if (say) the power-supply in your server fails you can check the WAL and compare it to the main database files to make sure everything is in a known state. > b) in docs say that after 7.2 seting this to false does'n turn off the > wall ...!? wich option does? The docs don't say that, as far as I can see. It doesn't make sense to turn off the WAL. -- Richard Huxton Archonet Ltd