Request a Demo
Home   >   mailing lists

Re: Should we allow ALTER OPERATOR CLASS to ADD/DROP operators and procedures? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Should we allow ALTER OPERATOR CLASS to ADD/DROP operators and procedures?
Date
Msg-id 1328356.1738887309@sss.pgh.pa.us
Whole thread Raw
In response to Should we allow ALTER OPERATOR CLASS to ADD/DROP operators and procedures?  (Tomas Vondra <tomas@vondra.me>)
List pgsql-hackers
Tree view 
Tomas Vondra <tomas@vondra.me> writes:
> Which is why PostGIS devs chose a different path - updating the catalogs
> to modify the opclass definition [3], using this script [4].

> That's a bit ... terrifying.

Indeed.  Did it not occur to them to use ALTER OPERATOR FAMILY?

The end result of doing so is that the added opfamily members
wouldn't have been bound tightly to the opclass, but that does
not seem like a huge deal in context.  They'd still have worked
fine AFAIK.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Should we allow ALTER OPERATOR CLASS to ADD/DROP operators and procedures?
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.