Re: Database/table limits ??????

I understand OID is signed integer which go up to 2^31.
Almost any case it would be sufficient. (It's sufficient for me, at least)

What I really want to know is the same as original poster.

> > 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?

Is this possible? If yes, how do I do it?

These are more important for most database admin for scalability and
performance, since PostgreSQL limits are large enough for most uses.

> OK, but what do I put there?

How about put a remark such as
- Except record(row) size, size of database objects are only limited by number OID
and host OS limitation.

(Sorry about my poor English.I'm not native. :-)

> > I looked at the FAQ also and IMO the word "unlimited" is a bit
> > unrealistic. "unlimited" means without limits. Come on now!
> > Postgres DOES have limits on the size of a database or table.
> > Very large limits but still limits. For example could I build
> > a table with 100 billion rows? No I'd run out of OIDs
> > I think you can say "In practice the limits are imposed by the
> > host OS and the processing power of current computers".
> >
> > Or with the number of columns in a table. You could say "The
> > row length limit imposes a practical limit of XX columns".
> >
> > You want to have unquestioned credibility so when you make fun
> > of the claims made by the MySQL people you are taken seriously.

I hope someone could answer my question.....

Yasuo Ohgaki
yasuo_ohgaki(at)hotmial(dot)com