| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| 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-08 00:20:15 |
| Message-ID: | 20030507192015.H66185@flake.decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)nasby(dot)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?"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Max Baker | 2003-05-08 00:23:40 | Re: age() and date intervals |
| Previous Message | Dennis Gearon | 2003-05-08 00:16:58 | Re: LC_COLLATE and index usage |