> > > I did like the alternative idea upthread of UUIDs for types which > > would give them a virtually unlimited space. > > Yeah, me too. That doesn't require a centralized authority (hence, no > debates here about whether a given extension is important enough to merit > an allocation of a given size), doesn't move us further in the direction of > exposing the database's internal identifiers as a concept that users have to > care about, ad provides essentially infinite address space. There's more > engineering work involved but sometimes more engineering work means a > better result. >
Random thought from the sideline... GIT is able to provide assurances as to content because it creates a hash. Now, for a function PostgreSQL could hash the catalog entry (including function body) and return than as proof that said function is the same as one installed in some other database or published publically. I do not know enough about the other objects to know if something similar is possible but maybe this will spark someone else's thoughts. David J. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
