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

> Jon,
> 
> > The nice thing about OIDs is that if you ever need to merge rows, you
> > could make a function that searched all OID-type parameters and
> > change the
> > old reference to the new one.
> 
> The same thing can be done with the 'universal_sq' approach.

How exactly?  The column types would just be INT8, right?

> Since you're undoubtedly familiar with PostgreSQL functions, I will list
> only how a stored procedure differes from a PgSQL function:
> 
> 1. Is precompiled, with a saved plan of execution on the server.
>     (not sure about the wisdom of this but it appears to be in the SQL 99
> standard)
> 2. Can return a rowset or multiple rowsets
> 3. Accepts an indefinite number of parameters
> 4. Returns an execution state and none to many return values
> 5. Supports full server control internally, depending on language; thus
> SQL and PL/pgSQL procedures should support cursors, locak handling,
> transactions and database control language.
> 

Aha!  The only thing I don't get is what do you mean by "execution state"?
(I'm guessing that you're not referring to Texas).

Jon