"Tom Lane" <[EMAIL PROTECTED]> writes: > The equivalent problem for views and functions is handled by restricting > CREATE OR REPLACE to not change the output column set of a view or the > type signature of a function, independently of whether there are any > actual references to the object. So maybe the right thing is that > CREATE OR REPLACE LANGUAGE can change "inessential" properties of an > existing language, but not the core properties --- which might only be > the handler function, though you could make a case for the validator and > the trusted flag as well.
I'm not so sure. What about if a PL language wants to include a version number in the language handler? Or if a new version has to change the name for some reason -- perhaps they discover that the old name doesn't work on some linkers for some reason. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches
