Re: maximum number of rows in table - what about oid limits?

> I've been thinking it should be a compile-time option.  But the protocol
> issue is going to be a problem.

The protocol issues shouldn't be a problem if you require separate
drivers.  Force clients to use libpq64.so.

The reason I'm concerned about this is that there are a _lot_ of great
things you can do with OIDs if they are unique.  For example, if you've
worked with Oracle Applications, they have this tacked on to the end of
all of their tables:

LAST_UPDATED_BY Int,
LAST_UPDATED_DATE Date,
...

Which could be replaced by a single table

Table UPDATE_HISTORY REFERRED_OBJECT OID, LAST_UPDATED_BY OID, LAST_UPDATED_DATE Date

which applies to all tables.  You could also have a notes table for
everything -

table NOTES REFERRED_OBJECT OID, Note Text

And so on and so forth.  However, with OID wrap-around, this would be
problematic.

Jon

> 
>             regards, tom lane
>