Re: BUG #13440: unaccent does not remove all diacritics
От | Andres Freund |
---|---|
Тема | Re: BUG #13440: unaccent does not remove all diacritics |
Дата | |
Msg-id | 20150618203818.GD29350@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: BUG #13440: unaccent does not remove all diacritics (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #13440: unaccent does not remove all diacritics
|
Список | pgsql-bugs |
On 2015-06-18 16:36:02 -0400, Tom Lane wrote: > Andres Freund <andres@anarazel.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...
В списке pgsql-bugs по дате отправления: