Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 6F1132E0043 for ; Fri, 16 May 2008 14:14:46 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 62856-04 for ; Fri, 16 May 2008 14:14:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by developer.postgresql.org (Postfix) with ESMTP id D17192E0033 for ; Fri, 16 May 2008 14:14:42 -0300 (ADT) Received: from jd-laptop (cmdalert.com [69.55.229.115]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m4GHFKcm007322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 May 2008 10:15:21 -0700 Date: Fri, 16 May 2008 10:15:05 -0700 From: "Joshua D. Drake" To: "Scott Marlowe" Cc: "Guillaume Cottenceau" , "Matthew Wakeling" , "pgsql-performance@postgresql.org" Subject: Re: which ext3 fs type should I use for postgresql Message-ID: <20080516101505.3e5814ed@jd-laptop> In-Reply-To: References: <1210846262.16664.41.camel@philippe-desktop> <482C4F3D.6010808@emolecules.com> <87ve1fwqov.fsf@mnc.ch> <87r6c3wpka.fsf@mnc.ch> <482C58EA.5090904@commandprompt.com> Organization: Joshua D. Drake X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.9; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/zR/eLg_dFv3cmah95=s51il"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Fri, 16 May 2008 10:15:39 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/246 X-Sequence-Number: 30214 --Sig_/zR/eLg_dFv3cmah95=s51il Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 16 May 2008 11:07:17 -0600 "Scott Marlowe" wrote: > Sorry, but that's like saying that open heart surgery isn't a fix for > clogged arteries because you should have been taking aspirin everyday > and exercising. It might not be the best answer, but sometimes it's > the only answer you've got. >=20 > I know that being able to drop the margin from x% to 0% for 10 minutes > has pulled more than one db back from the brink for me (usually > consulting on other people's databases, only once or so on my own) :) My point is, if you are adjusting that parameter you probably have a stray log or a bunch of rpms etc... that can be truncated to get you where you need to be. Of course there is always the last ditch effort of what you suggest but first you should look for the more obvious possible solution. Sincerely, Joshua D. Drake --=20 The PostgreSQL Company since 1997: http://www.commandprompt.com/=20 PostgreSQL Community Conference: http://www.postgresqlconference.org/ United States PostgreSQL Association: http://www.postgresql.us/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate --Sig_/zR/eLg_dFv3cmah95=s51il Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFILcEZATb/zqfZUUQRAtX7AJ0QePYRCzLeIPQDIl/UVCAQ/nY/XQCfT40q sPlvr+yDUKoE1unsc1IocDk= =ONhN -----END PGP SIGNATURE----- --Sig_/zR/eLg_dFv3cmah95=s51il--