| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Léonard Benedetti <benedetti(at)mlpo(dot)fr>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13440: unaccent does not remove all diacritics |
| Date: | 2016-02-16 14:47:21 |
| Message-ID: | 20160216144721.GD31273@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Feb 12, 2016 at 07:44:22PM +0300, Teodor Sigaev wrote:
> >>So I changed the script to handle special cases, and I added those I
> >>just mentioned (you will find attached the new version of the script
> >>and the generated output for convenience).
> >
> >Here is the patch, attached.
>
> I'm inclining to commit this patch becouse it suggests more regular
> way to update unaccent rules. That is nice.
>
> But I have some notices:
> 1 Is it possible to do not restrict generator script to Python V2?
> Python V2, seems, will go away in near future, and it will not be
> comfortable to install V2 for a single task.
> 2 As it's easy to see, nowhere in sources of pgsql there is no a
> UTF-8 encoding, just ASCII. I don't see reason to make an exception
> for this script.
How would this affect pg_trgm indexes upgraded by pg_upgrade?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Puckett | 2016-02-16 15:13:59 | aparent bug with pgAdmin version 1.22.1 connected to pg 9.5: SQL Pane view of SEQUENCE object |
| Previous Message | miha.vrhovnik | 2016-02-16 09:13:11 | BUG #13963: pg_clusterupgrade and materialized view |