From: Dimitri Fontaine <dfontaine@hi-media.com>
To: tony@exquisiteimages.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Architecting a database
Organization: Hi-Media
References: 
 <4f262829ce5efd2bc0296ef8a081cc41.squirrel@www.exquisiteimages.com>
User-Mail-Address: dfontaine@hi-media.com
Date: Mon, 28 Jun 2010 10:01:19 +0200
In-Reply-To: 
 <4f262829ce5efd2bc0296ef8a081cc41.squirrel@www.exquisiteimages.com>
	(tony@exquisiteimages.com's message of "Fri, 25 Jun 2010 15:36:07
	-0400")
Message-ID: <87tyonsi0g.fsf@hi-media-techno.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

tony@exquisiteimages.com writes:
> I am wondering how I should architect this in PostgreSQL. Should I follow
> a similar strategy and have a separate database for each client and one
> database that contains the global data? 

As others said already, there's more problems to foresee doing so that
there are advantages. If you must separate data for security concerns,
your situation would be much more comfortable using schema.

If it's all about performances, see about partitioning the data, and
maybe not even on the client id but monthly, e.g., depending on the
queries you run in your application.

Regards,
-- 
dim