Re: Many little databases or one big one? - Mailing list pgsql-general

From Bruno Wolff III
Subject Re: Many little databases or one big one?
Date
Msg-id 20030506013127.GB8384@wolff.to
Whole thread Raw
In response to Many little databases or one big one?  (Jason Hihn <jhihn@paytimepayroll.com>)
List pgsql-general
On Mon, May 05, 2003 at 16:04:24 -0400,
  Jason Hihn <jhihn@paytimepayroll.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.


pgsql-general by date:

Previous
From: "Scott W. Hill"
Date:
Subject: Importing Data into an Old Version of Postgres
Next
From: Drew Wilson
Date:
Subject: how to restrict inner results in OUTER JOIN?