Skip site navigation (1) Skip section navigation (2)

Re: Postgres Design

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: "Morris N(dot) Grajower" <morris(at)crosstab(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgres Design
Date: 2004-11-30 23:15:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
Speaking in a general sense, it's almost never a good idea to split
something across databases by an arbitrary boundary such as year. It's
also not a good idea to split things into multiple databases across
logical boundaries unless there's a compelling reason to do so.

On Tue, Nov 30, 2004 at 02:27:32PM -0500, Morris N. Grajower wrote:
> I have hundreds of different survey files in a customized database.
> I would like to convert them to postgres.
> My question is should I create one database for all the surveys or 
> should I limit the number of surveys to a database.
> for example create a different database for each survey year, or by 
> research company ?
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>      subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>      message can get through to the mailing list cleanly

Jim C. Nasby, Database Consultant               decibel(at)decibel(dot)org 
Give your computer some brain candy! Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

In response to

pgsql-general by date

Next:From: barbaraDate: 2004-11-30 23:46:09
Subject: Re: [ANNOUNCE] USENET vs Mailing Lists Poll ...
Previous:From: Dann CorbitDate: 2004-11-30 23:03:37
Subject: Re: change natural column order

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group