I said:
> It's likely that there are some pg_proc entries that you can break the
> system beyond repair by renaming, but I'd expect they are a relatively
> small minority (the system's hardwired references are by OID not name).
Just for fun I tried
d=# update pg_proc set proname = 'z' || proname;
UPDATE 1727
The database got a bit unpleasant to use, mainly because most of
psql's \d commands broke:
d=# \d foo
ERROR: function pg_catalog.pg_table_is_visible(oid) does not exist
but standard SQL operations still worked, and in fact I was able to
undo the damage with
d=# update pg_proc set proname = zsubstring(proname,2);
UPDATE 1727
So I say there isn't any reason to prohibit renaming functions just
because they were created at initdb time. The worst-case scenario
is you have to rename 'em back. Likewise for ALTER OWNER.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
