Robert Haas <robertmh...@gmail.com> writes: > On Mon, Feb 17, 2014 at 3:56 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> We should probably expend some thought on a general approach to >> replacing the default opclass for a datatype, because I'm sure this >> will come up again. Right now I don't see a feasible way.
> It seems odd for "default" to be a property of the opclass rather than > a separate knob. What comes to mind is something like: > ALTER TYPE sniffle SET DEFAULT OPERATOR CLASS FOR btree TO achoo_ops; > Not sure how much that helps. Not at all, AFAICS. If it were okay to decide that some formerly-default opclass is no longer default, then having such a command would be better than manually manipulating pg_opclass.opcdefault --- but extension upgrade scripts could certainly do the latter if they had to. The problem here is whether it's upgrade-safe to make such a change at all; having syntactic sugar doesn't make it safer. regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers