Re: tsearch_core for inclusion - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: tsearch_core for inclusion
Date
Msg-id 45FA14CB.6000601@commandprompt.com
Whole thread Raw
In response to Re: tsearch_core for inclusion  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: tsearch_core for inclusion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> +1 (again) Although I would see something like this:
>> CREATE INDEX fti1 on t1(c1) USING FULLTEXT [WITH] GIST | GIN
> 
> Surely the CREATE INDEX syntax has got enough warts on it already.
> Can't we express this as a particular operator class, or something
> that doesn't add any new syntax?

Do you mean something like:

CREATE INDEX fti1 ON t1 USING GIST|GIN(c1) WITH (FULLTEXT)

The above I got from the idea of FILLFACTOR so you could have something
like WITH (FILLFACTOR = 70, FULLTEXT) (not even sure if that is relevant)

OR

CREATE INDEX ftil ON t1 USING GIST|GIN(C1 FULLTEXT);

Where FULLTEXT is like VARCHAR OPS?

I could live with that.

Sincerely,

Joshua D. Drake




> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 


-- 
     === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997            http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: tsearch_core for inclusion
Next
From: Tom Lane
Date:
Subject: Re: tsearch_core for inclusion