Skip site navigation (1) Skip section navigation (2)

Re: Text Search zero padding

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Richard Greenwood <richard(dot)greenwood(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Text Search zero padding
Date: 2008-02-29 10:11:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On Fri, 29 Feb 2008, Richard Huxton wrote:

> Oleg Bartunov wrote:
>> On Thu, 28 Feb 2008, Richard Greenwood wrote:
>>> So far my best idea is to create a tsvector column containing both
>>> padded and non-padded versions of the value. i.e. put both R1234 and
>>> R0001234 into the tsvector column. This seems pretty brute force, and
>>> I am pretty new to text search, so I'd welcome any suggestions.
>> create your dictionary, which index R0001234 as R0001234 and R1234
>> Seems, dict_regex is your friend.
> Nice - I was thinking something like that would be useful, but Googling 
> hadn't found me anything. Thanks for that link Oleg.
> Wouldn't it be more efficient to have the regex-dictionary map just to R1234 
> though? Or R0001234, I suppose.

sure. But having both variants in index allows more flexible searches using
different configurations with/without mapping. Thinks about 'exact' search.


Oleg Bartunov, Research Scientist, Head of AstroNet (,
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su,
phone: +007(495)939-16-83, +007(495)939-23-83

In response to

pgsql-general by date

Next:From: Martijn van OosterhoutDate: 2008-02-29 10:25:41
Subject: Re: LIMIT Question
Previous:From: Tim RuppDate: 2008-02-29 10:08:39
Subject: Re: rule question

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group