| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)enterprisedb(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 01:40:59 |
| Message-ID: | 20150903014059.GA2912@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
Hmm, so what happens if you pg_upgrade FTS indexes? Are they somehow
marked invalid and a REINDEX is forced?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-09-03 02:52:18 | Re: error on online backup using pg_basebackup tool |
| Previous Message | Gerdan Rezende dos Santos | 2015-09-03 01:31:19 | error on online backup using pg_basebackup tool |