Re: many schemas or many databases

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Thomas Markus <t(dot)markus(at)proventis(dot)net>
Cc: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: many schemas or many databases
Date: 2011-02-08 09:42:46
Message-ID: AANLkTi=2fXzDE1KuenuJKuFM06z=QjMzwxvtsmKrecfz@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi

2011/2/8 Thomas Markus <t(dot)markus(at)proventis(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message OTSUKA Kenji 2011-02-08 09:45:11 about PostgreSQL 9.0.3 RPMs
Previous Message Itagaki Takahiro 2011-02-08 09:22:18 Re: [HACKERS] Issues with generate_series using integer boundaries