Re: BUG #13440: unaccent does not remove all diacritics - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #13440: unaccent does not remove all diacritics
Date
Msg-id 20150618202135.GB29350@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #13440: unaccent does not remove all diacritics  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #13440: unaccent does not remove all diacritics  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2015-06-18 15:30:46 -0400, Tom Lane wrote:
> Yeah, if we do anything other than adding new mappings, I suspect that
> part could not be back-patched.  Maybe adding new mappings shouldn't
> be back-patched either, though it seems relatively safe to me.

Hm. Why is it safe to add new mappings? If previously something has been
indexed with accents because unaccent didn't remove them and you're now
adding a new mapping to unaccent, the tsearch query will lookup the
wrong key (with accents removed)?

Greetings,

Andres Freund

pgsql-bugs by date:

Previous
From: chris+postgresql@qwirx.com
Date:
Subject: BUG #13454: Embedded python can stop WAL streaming and hot standby mode
Next
From: Tom Lane
Date:
Subject: Re: BUG #13440: unaccent does not remove all diacritics