Re: Architecting a database - Mailing list pgsql-performance

From Dimitri Fontaine
Subject Re: Architecting a database
Date
Msg-id 87tyonsi0g.fsf@hi-media-techno.com
Whole thread Raw
In response to Architecting a database  (tony@exquisiteimages.com)
Responses Re: Architecting a database
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Architecting a database
Next
From: Rajesh Kumar Mallah
Date:
Subject: order by slowing down a query by 80 times