> 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.
In response to
pgsql-performance by date
|Next:||From: Rajesh Kumar Mallah||Date: 2010-06-28 11:08:41|
|Subject: order by slowing down a query by 80 times|
|Previous:||From: Merlin Moncure||Date: 2010-06-26 15:49:27|
|Subject: Re: Architecting a database|