| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Gradek <mike(at)busbud(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13440: unaccent does not remove all diacritics |
| Date: | 2015-09-03 00:06:15 |
| Message-ID: | 20150903000615.GC17210@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2015-09-02 19:59:37 -0400, Tom Lane wrote:
> No, not after someone pointed out that it could have strange side-effects
> on full text search configurations that used unaccent. You'd stop being
> able to find documents whenever your search term is stripped of accents
> more thoroughly than before. That might be all right in a new major
> release (if it documents that you might have to rebuild your FTS indexes
> and derived tsvector columns). It's not all right in a minor release.
Yes, it was me that pointed that out and argued against it ;)
http://archives.postgresql.org/message-id/20150618202135.GB29350%40alap3.anarazel.de
and following.
Thomas, will you repost context & a patch implementing this (instead of
just files)?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerdan Rezende dos Santos | 2015-09-03 01:28:07 | error on online backup using pg_basebackup tool |
| Previous Message | Tom Lane | 2015-09-02 23:59:37 | Re: BUG #13440: unaccent does not remove all diacritics |