Re: How do we support FULL JOIN on PostGIS types? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: How do we support FULL JOIN on PostGIS types?
Date
Msg-id 28099.1559570174@sss.pgh.pa.us
Whole thread Raw
In response to Re: How do we support FULL JOIN on PostGIS types?  (Darafei "Komяpa" Praliaskouski <me@komzpa.net>)
List pgsql-hackers
=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?= <me@komzpa.net> writes:
> Thanks a lot RhodiumToad on IRC for suggestion of setting HASHES, MERGES on
> OPERATOR =.
> Now we have other problem: how do we set these flags on upgrade to new
> version of extension? Dropping an OPERATOR = will drop all indexes an views
> depending on it so isn't really an option.

I think you're going to have to use a direct UPDATE on pg_operator in
the extension update script :-(.  Perhaps ALTER OPERATOR should be able
to handle changing these flags, but for now it can't.

            regards, tom lane



pgsql-hackers by date:

Previous
From: James Coleman
Date:
Subject: Re: [PATCH] Incremental sort (was: PoC: Partial sort)
Next
From: Dave Cramer
Date:
Subject: Binary support for pgoutput plugin