| From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Prefix operator for text and spgist support |
| Date: | 2018-04-16 10:45:23 |
| Message-ID: | CAE2gYzw0i2ejZrS5y2-PVbe7qBE3deNAC1dLaFT75hNEgxZRUA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Thank you, pushed with some editorization and renaming text_startswith to
> starts_with
I am sorry for not noticing this before, but what is the point of this
operator? It seems to me we are only making the prefix searching
business, which is already complicated, more complicated.
Also, the new operator is not documented on SQL String Functions and
Operators table. It is not supported by btree text_pattern_ops or
btree indexes with COLLATE "C". It is not defined for "citext", so
people would get wrong results. It doesn't use pg_trgm indexes
whereas LIKE can.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2018-04-16 11:11:17 | Re: Postgres stucks in deadlock detection |
| Previous Message | Martin Swiech | 2018-04-16 10:40:54 | Postgres 10 problem with UNION ALL of null value in "subselect" |