Re: many schemas or many databases - Mailing list pgsql-general

From Pavel Stehule
Subject Re: many schemas or many databases
Date
Msg-id AANLkTi=2fXzDE1KuenuJKuFM06z=QjMzwxvtsmKrecfz@mail.gmail.com
Whole thread Raw
In response to Re: many schemas or many databases  (Thomas Markus <t.markus@proventis.net>)
Responses Re: many schemas or many databases  (Ivano Luberti <luberti@archicoop.it>)
List pgsql-general
Hi

2011/2/8 Thomas Markus <t.markus@proventis.net>:
> hi,
>
> i would prefer many schemas. advantages:
> - one backup/restore for all (or selective)
> - one connection pool
> - simple access to all schemas
>

+1

and one disadvantage

- impossible separation on independent hw, when it is necessary or
when you has more hw

Depends on application and size of data - if you has lot of logs, or
some like OLAP data, then is very practical use more than one
database.

Regards

Pavel Stehule

> regards
> thomas
>
>
> Am 08.02.2011 09:30, schrieb Szymon Guz:
>>
>> Hi,
>> is there any noticeable difference between a cluster with many databases
>> and
>> a database with many schemas?
>>
>> I've got a quite huge database on Oracle with about 400 logically disjoint
>> schemas.
>> I could import that into PostgreSQL as many different databases, or as one
>> database with many schemas.
>>
>>  From the application point of view it could be easier to have different
>> databases, as for now the applications log in into different schemas, so
>> this behavior wouldn't change.
>>
>> Do you see any drawbacks of any of the solutions?
>>
>>
>> regards
>> Szymon
>>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

pgsql-general by date:

Previous
From: Thomas Markus
Date:
Subject: Re: many schemas or many databases
Next
From: OTSUKA Kenji
Date:
Subject: about PostgreSQL 9.0.3 RPMs