From: Dimitri Fontaine <dfontaine@hi-media.com>
To: tony@exquisiteimages.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Architecting a database
Date: Mon, 28 Jun 2010 10:01:19 +0200
Message-ID: <87tyonsi0g.fsf@hi-media-techno.com> (raw)
In-Reply-To: <4f262829ce5efd2bc0296ef8a081cc41.squirrel@www.exquisiteimages.com>
References: <4f262829ce5efd2bc0296ef8a081cc41.squirrel@www.exquisiteimages.com>
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
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dfontaine@hi-media.com, tony@exquisiteimages.com
Subject: Re: Architecting a database
In-Reply-To: <87tyonsi0g.fsf@hi-media-techno.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