From: | "zhuxiang" <xiang(dot)zhu(at)alibaba-inc(dot)com> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <teodor(at)sigaev(dot)ru> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | support extending indexscan,heapscan and customizing plan |
Date: | 2008-11-18 09:23:38 |
Message-ID: | 000c01c9495f$573b61c0$0f8e3e0a@yahoo.ali.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
we currently want to employ PG and Gin Index for light-weight full text
search engine. however,
we encounter a problem that Gin Index is not quick enough for relevence,
because it must
scan all heaptuples which statisfy the condition, then invoke ts_rank to
compute the rank of tuple.
an idea comes to us: add some foundamental ranking features to the Gin index
structure;
then we can find the most relevance tuples just from index, which result in
a problem that we must
add a type of indexscan and heapscan,customize plan. but PG don't support
the behaviors,.
As far as I know, oracle support customizing plan. My question is how can i
slove it, and whether PG
will support extending indexscan and heapscan,customizing plan in future.
Thanks
--zhuxiang
Yahoo! CN
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-11-18 10:10:02 | Re: Updates of SE-PostgreSQL 8.4devel patches (r1197) |
Previous Message | KaiGai Kohei | 2008-11-18 09:02:00 | Re: Updates of SE-PostgreSQL 8.4devel patches (r1197) |