Tom Lane wrote: > To my mind though, the lack of an ALTER OPERATOR SET FUNCTION command > is on par with our very limited ability to alter the contents of > an operator class. In principle it would be nice, but the practical > value is so small that it's not surprising it hasn't been done --- > and we shouldn't continue to hold the door open for a simple way of > implementing it when there are significant costs to doing so.
I think allowing an operator's implementation function to change would be rather problematic, would it not? There's no way to know whether the semantic changes to stored rules would make sense, not least because the person running ALTER OPERATOR wouldn't know (== has no easy way to find out) what is being changed in the first place. To me, it looks like we should just not allow ALTER OPERATOR SET FUNCTION to be implemented at all. It's not like changing an operator's implementation is an oft-requested feature anyway. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
