Re: KEEPONLYALNUM for pg_trgm is not documented

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: KEEPONLYALNUM for pg_trgm is not documented
Date: 2011-09-05 17:25:40
Message-ID: 201109051725.p85HPeG20771@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> On Fri, Mar 11, 2011 at 3:59 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> > On Fri, Mar 11, 2011 at 5:52 PM, Itagaki Takahiro
> > <itagaki(dot)takahiro(at)gmail(dot)com> wrote:
> >> contrib/pg_trgm in 9.1 becomes more attractive feature by index supports
> >> for LIKE operators, but only alphabet and numeric characters are indexed
> >> by default. But, we can modify KEEPONLYALNUM in the source code to
> >> keep all characters in n-gram words.
> >>
> >> However, the limitation and KEEPONLYALNUM are not documented in the page:
> >> ?http://developer.postgresql.org/pgdocs/postgres/pgtrgm.html
> >>
> >> An additonal documentation patches acceptable? The issues would be a FAQ for
> >> non-English users. I heard that pg_trgm will be one of the *killer features*
> >> of 9.1 in Japan, where N-gram based text search is preferred.
> >
> > +10
>
> It's certainly not too late for doc patches.

I have applied the attached documention patch to 9.0, 9.1, and current
to mention that only ascii alphanumeric characters are processed by
contrib/pg_trgm.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Attachment Content-Type Size
/rtmp/diff text/x-diff 774 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message hubert depesz lubaczewski 2011-09-05 17:52:16 Re: [GENERAL] pg_upgrade problem
Previous Message Andy Colson 2011-09-05 17:17:20 regular logging of checkpoint progress