Re: Architecting a database

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: tony(at)exquisiteimages(dot)com
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Architecting a database
Date: 2010-06-28 08:01:19
Message-ID: 87tyonsi0g.fsf@hi-media-techno.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

tony(at)exquisiteimages(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rajesh Kumar Mallah 2010-06-28 11:08:41 order by slowing down a query by 80 times
Previous Message Merlin Moncure 2010-06-26 15:49:27 Re: Architecting a database