Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm
Date: 2013-04-07 18:02:38
Message-ID: CAPpHfdu=NSVTfPWaUcYQdns7Ah4iFV1uP93ROGqwftHFvr0qpA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 7, 2013 at 10:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Alexander Korotkov <aekorotkov(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-04-07 18:47:07 pgsql: Get rid of USE_WIDE_UPPER_LOWER dependency in trigram constructi
Previous Message Tom Lane 2013-04-07 18:00:17 Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm