From: | David Smith <gegez-pgh(at)instytut(dot)com(dot)pl> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | creating index on changed field type |
Date: | 2004-03-11 18:23:48 |
Message-ID: | 4050AEB4.9050205@instytut.com.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
the subject is obscure, so I will try to explain. I would like to
develop index based on text field (or tsvector stolen from tsearch2),
but containing different type (for example cstring, varchar,etc.) in
order to tokenize the original field. I would like to use postgresql
btree implementation, but AFAICS I can not do it. Example:
CREATE TABLE test (id int, mytext text);
CREATE INDEX myindex on test USING myindex (mytext) ;
INSERT INTO test VALUES(1,'this is my first text');
In index I do not want to keep whole phrase, but words derived from it
('this', 'is', 'my', 'first', 'text').
My idea was to create functions mybtgettuple, mybtinsert, mybtbeginscan
, mybtrescan and so on. And in every case ignoring original
IndexTuple, and create set of new IndexTuple's (one for every term) and
involving original functiions.
The problem is that index_create() in catalog/index.c creates everything
in system tables, especially type of index field.
Should I forget about btrees and move to GIST, or is there any hack,
which could solve my problem? Please help me.
Thanks in advance,
David
ps. maybe I should create index on TEXT field, store terms (words form
the original field) also as TEXT type? Will it work?
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-03-11 18:41:58 | Re: Default Stats Revisited |
Previous Message | scott.marlowe | 2004-03-11 18:06:40 | Re: Default Stats Revisited |