Postgres Pro
Downloads
Home   >   mailing lists

Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm
Date
Msg-id 24336.1365357617@sss.pgh.pa.us
Whole thread Raw
In response to Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm
List pgsql-hackers
Tree view 
Alexander Korotkov <aekorotkov@gmail.com> writes:
> It's also likely we can change
>    if (pg_database_encoding_max_length() > 1)
> into something like
>    if (pg_database_encoding_max_length() > 1 && bytelen != charlen)

Hm, actually couldn't we just simplify to "if (bytelen != charlen)"?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm
Next
From: Alexander Korotkov
Date:
Subject: Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm