n Mon, Dec 27, 2010 at 1:23 PM, Joel Jacobson <j...@gluefinance.com> wrote: > I'm working on a tool to simplify updating the source code of database > functions. > To do a "revert" my plan is to store the values of pg_proc.* before > updating, and then to restore pg_proc for the given oid if a revert is > necessary. > This raises the question, > Is it "safe" to do, > UPDATE pg_proc SET <column> = <new source code> WHERE oid = <function's > oid>; > instead of using the "CREATE OR REPLACE FUNCTION" command?
I'm not immediately sure whether it's safe, but it seems like playing with fire, and I don't see any particular advantage to doing it this way over using CREATE OR REPLACE FUNCTION. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
