| 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-06-18 20:38:18 |
| Message-ID: | 20150618203818.GD29350@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2015-06-18 16:36:02 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2015-06-18 16:30:46 -0400, Tom Lane wrote:
> >> This is the same situation as any change whatsoever to tsearch
> >> dictionaries. The party line on that is that it usually doesn't
> >> matter much, and if it does you can rebuild your indexes.
>
> > I think that's an acceptable answer if the user changes their
> > dictionary, but if we do it for them it's different.
>
> So you're arguing that unaccent.rules is forever frozen, no matter whether
> it's obviously broken or not?
I think it's perfectly sensible to update the rules in master (even if
that has consequences for pg_upgraded databases). I'm just doubtful
about the merits of backpatching changes like this. But I'm not going to
fight hard/any further...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-06-18 20:48:44 | Re: BUG #13440: unaccent does not remove all diacritics |
| Previous Message | Tom Lane | 2015-06-18 20:36:02 | Re: BUG #13440: unaccent does not remove all diacritics |