[EMAIL PROTECTED] wrote:
>
> pgsql-admin-digest Monday, November 22 1999 Volume 01 : Number 392
>
> Index:
>
> Database/table limits ??????
>
> ----------------------------------------------------------------------
>
> Date: Mon, 22 Nov 1999 12:13:31 -0700
> From: hal Lynch <[EMAIL PROTECTED]>
> Subject: Database/table limits ??????
>
> I am running postgresql 6.5.2 on FreeBSD. I am developing a data warehouse
> here at Utah State University. A quick look at the docs leaves the following
> questions:
>
> 1. what is the maximum size for a database?
> 2. what is the maximum size for a table?
> 3. what is the maximum size for a row?
> 4. What is the maximum number of rows in a table?
> 5. What is the maximum number of items in a row/table?
> 6. What is the maximun number of indexes to a table;
> 7. What is the maximum size of an index file?
> 8. Can a database be spread over more than one disk drive?
> 9. Can a table be spread over more than one disk drive?
> If the answer to 8 and or 9 is yes, how do I do it?
Yes you can do this. The answer is "RAID". I use Postgres
mostly on Linux and some with Solaris/SPARC. On Linux I
can make a large file system that spans several physical
disks. Lacking an OS with built-in software RAID you could
simply database tables and use links to point to them.
One __major__ limit with Postgres is that it uses 32 bit
integer counters called an "OID" each row must have a
unique OID and the OID must be unique within an intire
Postgres installation. This means only a few billion
rows and index entries in an entire database. I hope
they dump this idea in a couple years or go to 64
bit OIDs
>
> I know I am asking a lot here, and would be satisfied with where in
> the docs to look.
>
> Thanks hal
>
> ------------------------------
>
> End of pgsql-admin-digest V1 #392
> *********************************
>
> ************
--
Chris Albertson
[EMAIL PROTECTED] Voice: 626-351-0089 X127
Logicon, Pasadena California Fax: 626-351-0699
************
