| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How do we support FULL JOIN on PostGIS types? |
| Date: | 2019-06-03 13:56:14 |
| Message-ID: | 28099.1559570174@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?= <me(at)komzpa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2019-06-03 14:49:54 | Binary support for pgoutput plugin |
| Previous Message | James Coleman | 2019-06-03 13:39:10 | Re: [PATCH] Incremental sort (was: PoC: Partial sort) |