Re: Many little databases or one big one?

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Jason Hihn <jhihn(at)paytimepayroll(dot)com>
Cc: Pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Many little databases or one big one?
Date: 2003-05-06 01:31:27
Message-ID: 20030506013127.GB8384@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, May 05, 2003 at 16:04:24 -0400,
Jason Hihn <jhihn(at)paytimepayroll(dot)com> wrote:
>
> What are the down sides? I know that I can no longer partition the data into
> separate directories. A table corruption would effect everyone. More data
> needs to be stored (addt'l keys). Are there other downsides? If there are
> too many down sides, is there an easier way I can update the db objects (a
> tool) for each DB all at once?

A script could fairly easily apply a set of identical changes to all of the
databases in one postmaster.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Drew Wilson 2003-05-06 04:40:10 how to restrict inner results in OUTER JOIN?
Previous Message Scott W. Hill 2003-05-06 01:25:48 Importing Data into an Old Version of Postgres