From: | Chris Potter <cpotter(at)pcisys(dot)net> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Is DB Limited To 1 File? |
Date: | 2000-02-19 07:42:08 |
Message-ID: | 38AE4950.F4B16212@pcisys.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
All:
I am very excited about this product after glancing through the
documentation. The object-relational capabilities seem very
intriguing. I have one substantial concern, however. Am I correct in
that the creation of a database is limited to 1 file? I am used to the
Sybase and Oracle world where databases span several disks in order to
leverage disk drive to controller relationships. I would think without
this capability there is the potential for major disk thrashing in
something as simple as a query for which the SQL optimizer chooses to
use an index. Chances are, I assume, the index would be on one portion
of the drive whereas the data would be on another. The ability to have
the index on a separate drive than the data would seem to be
monumentally beneficial. I realize the intent for OLTP transaction
mixes is that the data would live in an in-memory cache, however, this
can't be guaranteed for very large databases.
Am I missing Something?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-02-19 14:13:06 | Re: [ADMIN] Backup of db with large objects. |
Previous Message | M.Mazurek | 2000-02-18 19:37:36 | Backup of db with large objects. |