pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shane Ambler <pgsql@007Marketing.com>
To: Ray Stell <stellr@cns.vt.edu>
Cc: Bruno Wolff III <bruno@wolff.to>
Cc: pgsql-admin@postgresql.org
Subject: Re: cluster or database?
Date: Mon, 29 Jan 2007 03:46:06 +1030
Message-ID: <45BCDA56.7000503@007Marketing.com> (raw)
In-Reply-To: <20070128142517.GA24908@cns.vt.edu>
References: <20070124193237.GA7143@cns.vt.edu>
	<20070127194252.GA4050@wolff.to>
	<20070128142517.GA24908@cns.vt.edu>

Ray Stell wrote:
> On Sat, Jan 27, 2007 at 01:42:52PM -0600, Bruno Wolff III wrote:
>> On Wed, Jan 24, 2007 at 14:32:37 -0500,
>>   Ray Stell <stellr@cns.vt.edu> wrote:
>>> Is there a drawback to have different clusters on the same
>>> system/diskspace?   I have different applications I want to support
>>> initially on the same server/disk array.  I was thinking it would be
>>> better/easier to have seperate clusters per app for ease of migration
>>> and security.  Is it highly superior just to use different dbs?  Why?
>>> Where is this discussed?  Thanks.
>> The downside to multiple clusters is that is harder to configure them
>> to play nice with each other in the way of resource utilization because
>> they don't communicate with each other.
> 
> 
> Thank you for responding.  Do you have any documentation that would
> support my efforts to understand some of the issues?
> 

You should probably start with
http://www.postgresql.org/docs/8.2/interactive/creating-cluster.html
which will explain more about what a cluster is.

http://www.postgresql.org/docs/8.2/interactive/kernel-resources.html
should give you some insight into the problems system resources can play 
with multiple servers on one machine.

There are a couple of ways you can have several clusters on one machine.
1. run initdb on different directories and start PostgreSQL with a 
different one (-D option) when you want to work with it (which may fit 
in with what you want to do).
2. run multiple copies of PostgreSQL each with it's own cluster, port 
and using more system resources.

2 is where the resource problems come in - each server will need a 
number of resources which is limited by system settings and often will 
need a recompiled kernel to allow higher limits.

You shouldn't have any problems developing multiple databases on the one 
server/cluster - each db is entirely separate from the others and you 
would only have problems if you are customizing the system catalog and 
want differences with each db you are working on.

When you come to install your db on the client server you create a new 
cluster for their server and create the users/groups they will use then 
create the database for them with the structure you want in it. You only 
need to transfer the one database structure from your development server 
not your entire cluster.



-- 

Shane Ambler
pgSQL@007Marketing.com

Get Sheeky @ http://Sheeky.Biz



view thread (4+ messages)

Message-ID: <45BCDA56.7000503@007Marketing.com>
Permalink:  ../45BCDA56.7000503@007Marketing.com/
Also on:    postgresql.org/message-id/45BCDA56.7000503@007Marketing.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: pgsql@007Marketing.com, stellr@cns.vt.edu, bruno@wolff.to
  Subject: Re: cluster or database?
  In-Reply-To: <45BCDA56.7000503@007Marketing.com>
  References: <20070124193237.GA7143@cns.vt.edu> <20070127194252.GA4050@wolff.to> <20070128142517.GA24908@cns.vt.edu> <45BCDA56.7000503@007Marketing.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox