| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: multibyte charater set in levenshtein function |
| Date: | 2010-05-12 19:04:18 |
| Message-ID: | 1273690962-sup-2257@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Alexander Korotkov's message of lun may 10 11:35:02 -0400 2010:
> Hackers,
>
> The current version of levenshtein function in fuzzystrmatch contrib modulte
> doesn't work properly with multibyte charater sets.
> My patch make this function works properly with multibyte charater sets.
Great. Please add it to the next commitfest:
http://commitfest.postgresql.org
On a quick look, I didn't like the way you separated the
"pg_database_encoding_max_length() > 1" cases. There seem to be too
much common code. Can that be refactored a bit better?
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2010-05-12 19:10:28 | Re: max_standby_delay considered harmful |
| Previous Message | Heikki Linnakangas | 2010-05-12 19:01:49 | Re: primary/secondary/master/slave/standby |