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

From Jim C. Nasby
Subject Re: Many little databases or one big one?
Date
Msg-id 20030507192015.H66185@flake.decibel.org
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 04:04:24PM -0400, Jason Hihn wrote:
> make views for each former database (after appending a key to each table,
> and appropriately naming the view). This would be much more manageable,

You need to be careful if performance is an issue. Because PGSQL doesn't
support clustered indexes/index organized tables, you can get into a
situation where you end up tablescanning instead of using the index to
access the particular set of data you want.

If you look in the performance archives for April, you'll see several
messages about this.
--
Jim C. Nasby (aka Decibel!)                    jim@nasby.net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net 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?"


pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: LC_COLLATE and index usage
Next
From: Max Baker
Date:
Subject: Re: age() and date intervals