From: | "MauMau" <maumau307(at)gmail(dot)com> |
---|---|
To: | "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>, "Euler Taveira" <euler(at)timbira(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Can pg_trgm handle non-alphanumeric characters? |
Date: | 2012-05-10 11:45:31 |
Message-ID: | 6A03E28C25F24EA1AD941E37DDFD90D5@maumau |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>
> On Thu, May 10, 2012 at 8:18 AM, Euler Taveira <euler(at)timbira(dot)com> wrote:
>> On 09-05-2012 19:17, MauMau wrote:
>>> Then, does it make sense to remove "#define KEEPONLYALNUM" in 9.1.4?
>>> Would it
>>> cause any problems? If no, I wish that, because it eliminates the need
>>> to do
>>> the removal every time the users applies minor releases.
>>>
>> If you do so, you'll break minor versions.
>
> Right. And removing KEEPONLYALNUM is a feature change rather than bug fix,
> so that should be proposed during major version development cycle.
For information, what kind of breakage would occur? Is it performance
degradation, extra index storage consumption, or undesirable query results?
I imagined removing KEEPONLYALNUM would just accept non-alphanumeric
characters and cause no harm to those who use only alphanumeric characters.
Regards
MauMau
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2012-05-10 12:11:54 | Re: Draft release notes complete |
Previous Message | Florian Pflug | 2012-05-10 11:43:01 | Re: Gsoc2012 idea, tablesample |