Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > Here's something not to forget in this whole business: the present TSearch2
> > implementation permits you to have a different tsvector configuration for
> > each *row*, not just each column. That is, applications can be built with
> > "per-cell" configs.
>
> Certainly. That's actually the easiest case to deal with, because you're
> going to put the tsvector config identity into another column of the
> table, and the trigger or index just references it there. It hasn't
> been part of the discussion because it's not a problem.
I added an example of that in the documentation (second query):
http://momjian.us/expire/textsearch/HTML/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
