Postgres Pro
Downloads
Home   >   mailing lists

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

From Alexander Korotkov
Subject Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm
Date
Msg-id CAPpHfdu=NSVTfPWaUcYQdns7Ah4iFV1uP93ROGqwftHFvr0qpA@mail.gmail.com
Whole thread Raw
In response to Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm
List pgsql-hackers
Tree view
On Sun, Apr 7, 2013 at 10:00 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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)"?

I think yes, we can :)

------
With best regards,
Alexander Korotkov.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm
Next
From: Tom Lane
Date:
Subject: Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm