Re: Slightly insane use of USE_WIDE_UPPER_LOWER in pg_trgm

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
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:48:24
Message-ID: 25887.1365360504@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> On Sun, Apr 7, 2013 at 10:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hm, actually couldn't we just simplify to "if (bytelen != charlen)"?

> I think yes, we can :)

OK. I pushed this as a separate commit so as to highlight the potential
incompatibility in the commit log. I am not sure it's even worth a
release note though ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kerem Kat 2013-04-07 18:52:03 Current syslogger filename
Previous Message Tom Lane 2013-04-07 18:47:07 pgsql: Get rid of USE_WIDE_UPPER_LOWER dependency in trigram constructi