X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 88F84475E6F for ; Thu, 20 Feb 2003 18:01:14 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 44813-05 for ; Thu, 20 Feb 2003 18:01:03 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 8FE16475C14 for ; Thu, 20 Feb 2003 17:33:23 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2849910; Thu, 20 Feb 2003 14:33:33 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Robert Treat Subject: Re: Tuning scenarios (was Changing the default configuration) Date: Thu, 20 Feb 2003 14:33:02 -0800 X-Mailer: KMail [version 1.4] References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <200302140936.02011.josh@agliodbs.com> <1045778701.14518.81.camel@camel> In-Reply-To: <1045778701.14518.81.camel@camel> Cc: pgsql-performance@postgresql.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200302201433.02654.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/140 X-Sequence-Number: 1196 Robert, > > 1) Location of the pg_xlog for heavy-update databases. >=20 > I see you put this up pretty high on the list. Do you feel this is the > most important thing you can do? For example, if you had a two drive > installation, would you load the OS and main database files on 1 disk > and put the pg_xlog on the second disk above all other configurations?= =20 Yes, actually. On machines with 2 IDE disks, I've found that this can mak= e=20 as much as 30% difference in speed of serial/large UPDATE statements. > Ideally I recommend 3 disks, one for os, one for data, one for xlog; but > if you only had 2 would the added speed benefits be worth the additional > recovery complexity (if you data/xlog are on the same disk, you have 1 > point of failure, one disk for backing up) On the other hand, with the xlog on a seperate disk, the xlog and the datab= ase=20 disks are unlikely to fail at the same time. So I don't personally see it = as=20 a recovery problem, but a benefit. --=20 -Josh Berkus Aglio Database Solutions San Francisco