Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 59E1A476242 for ; Fri, 24 Jan 2003 18:28:38 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 2BB1A476246 for ; Fri, 24 Jan 2003 18:21:50 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2324884; Fri, 24 Jan 2003 15:21:56 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Noah Silverman , pgsql-performance@postgresql.org Subject: Re: Multiple databases one directory Date: Fri, 24 Jan 2003 15:22:28 -0800 X-Mailer: KMail [version 1.4] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301241522.28521.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/296 X-Sequence-Number: 943 Noah, > Would there be an advantage to putting each of the two databases into a= =20 > separate directory and starting two instances of postgres? Is it=20 > better to just lump everything together. You can use the WITH LOCATION option in CREATE DATABASE to put the two=20 databases into seperate directories *without* running two instances of=20 postgres. For that matter, the databases each have their own directories, by OID numb= er. Of course, this only helps you if the seperate directories are on seperate= =20 disks/arrays/channels. If everying is on the same disk or array, don't=20 bother. --=20 -Josh Berkus Aglio Database Solutions San Francisco