| From: | Oleg Bartunov <obartunov(at)postgrespro(dot)ru> |
|---|---|
| To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | remove deprecated @@@ operator ? |
| Date: | 2018-10-21 20:14:34 |
| Message-ID: | CAF4Au4wmUsZRVhR+ySpvabRfB_1D1fnrPY9TRAKO2DEbi4Cpgg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Hello,
The commit 9b5c8d45f62bd3d243a40cc84deb93893f2f5122 is now 10+ years
old, may be we could remove deprecated @@@ operator ?
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Mon Apr 14 17:05:34 2008 +0000
Push index operator lossiness determination down to GIST/GIN opclass
"consistent" functions, and remove pg_amop.opreqcheck, as per recent
discussion. The main immediate benefit of this is that we no longer need
8.3's ugly hack of requiring @@@ rather than @@ to test weight-using tsquery
searches on GIN indexes. In future it should be possible to optimize some
other queries better than is done now, by detecting at runtime whether the
index match is exact or not.
Tom Lane, after an idea of Heikki's, and with some help from Teodor.
Best Regards,
Oleg
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-10-21 20:24:16 | Re: remove deprecated @@@ operator ? |
| Previous Message | Pablo Benito | 2018-10-21 00:37:56 | Re: The DROP TABLE instruction should have a TEMP option for when a temporary table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-10-21 20:24:16 | Re: remove deprecated @@@ operator ? |
| Previous Message | Paul A Jungwirth | 2018-10-21 19:46:58 | Re: SQL:2011 PERIODS vs Postgres Ranges? |