On Thu, Feb 27, 2014 at 5:30 PM, Tom Lane <[email protected]> wrote: > Indeed. The root of the problem here is that we've never really thought > about changing a type's default opclass before. I don't think that a > two-line change in pg_dump fixes all the issues this will bring up.
I think we did actually do this once. When you replaced rtree with gist as the default opclass for the rtree method. IIRC you did it by making "rtree" a synonym for "gist" and since the opclass wasn't specified the default gist opclass kicked in automatically. -- greg -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
