| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tsearch_core for inclusion |
| Date: | 2007-03-16 04:11:45 |
| Message-ID: | 964.1174018305@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> Surely the CREATE INDEX syntax has got enough warts on it already.
> Do you mean something like:
> CREATE INDEX ftil ON t1 USING GIST|GIN(C1 FULLTEXT);
> Where FULLTEXT is like VARCHAR OPS?
Yeah, that one. It might be more consistent to spell it as "fulltext_ops"
but I wouldn't insist on it.
Of course the issue not addressed here is where you specify all the
secondary configuration data (the stuff currently handled by config
tables in the contrib implementation). Perhaps the WITH clause would
work for that, though in the current code WITH is targeted at the index
AM not individual opclasses.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2007-03-16 04:12:32 | Re: As proposed the complete changes to pg_trigger and pg_rewrite |
| Previous Message | Joshua D. Drake | 2007-03-16 03:53:47 | Re: tsearch_core for inclusion |