From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "'Michael Cheung *EXTERN*'" <vividy(at)justware(dot)co(dot)jp>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: schema or database |
Date: | 2015-04-13 08:43:50 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B365CC78D@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Cheung wrote:
> I have many similar database to store data for every customer.
> Structure of database is almost the same.
> As I use same application to control all these data, so I can only use
> one database user to connect to these database.
> And I have no needs to query table for different customer together.
>
> I wonder which I should use, different shema or different database to store data?
>
> I 'd like to know the advantage and disadvantage for using schema or database.
In addition to what others have said:
If you use multiple schemas within one database, the danger is greater that
data are written to or read from the wrong schema if your application has a bug
ans does not make sure to always set search_path or qualify every access with a
schema name.
With multiple databases you are guaranteed not to access data from a different
database.
The main downside that I see to multiple databases is the overhead: each of
the databases will have its own pg_catalog tables.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-04-13 08:48:48 | Re: schema or database |
Previous Message | David G. Johnston | 2015-04-13 07:33:59 | Re: Limiting user from changing its own attributes |