Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 136CC9FB43A for ; Fri, 16 Feb 2007 17:56:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 45354-03 for ; Fri, 16 Feb 2007 17:56:40 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 1839F9FB406 for ; Fri, 16 Feb 2007 17:56:42 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Fri, 16 Feb 2007 21:56:41 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 16 Feb 2007 15:56:41 -0600 Subject: Re: Isolated databases or instances From: Scott Marlowe To: Tom Lane Cc: "Henry, Nigel, CYFD" , pgsql-admin@postgresql.org In-Reply-To: <7692.1171660568@sss.pgh.pa.us> References: <2488267002735E4293095085A7B5D86401446CAA@CEXMB4.nmes.lcl> <1171655529.3565.89.camel@state.g2switchworks.com> <7692.1171660568@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1171663001.3565.106.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 16 Feb 2007 15:56:41 -0600 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.023 tagged_above=0 required=5 tests=AWL, BAYES_50, SPF_PASS, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200702/243 X-Sequence-Number: 24708 On Fri, 2007-02-16 at 15:16, Tom Lane wrote: > Scott Marlowe writes: > > On Fri, 2007-02-16 at 13:18, Henry, Nigel, CYFD wrote: > >> We are at the beginning of the building of a 3-tier > >> development/test/uat environment. We would like some advice on how > >> the PostgreSQL database should be configured for this environment. > > > What exactly are you trying to accomplish with multiple PostgreSQL > > instances here? I can't see there being any great advantage to three > > separate instances than having three discrete databases defined in one > > instance. > > Separating development and production instances seems perfectly sensible > to me. For instance, if your development code triggers a crash in > Postgres, you don't really want that event to take out your production > sessions. Also, you might want to run Postgres version x+1 for awhile > as development before replacing version x for production. I agree. (Note that this is dev/test/uat, not prod/dev). But it really depends on his usage patterns and such. If he's not planning on doing any functions in C, and assuming that testing of things like pgsql / jboss / apache will be done on another system entirely, then it might well be easier to run everything from one database server. I think we need to know more about the planned usage to really say one way or the other.