Re: tsearch2 in PostgreSQL 8.3?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Subject: Re: tsearch2 in PostgreSQL 8.3?
Date: 2007-08-17 17:16:57
Message-ID: 200708171716.l7HHGvq21323@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> 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 <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2007-08-17 17:28:13 Re: [HACKERS] Re: cvsweb busted (was Re: pgsql: Repair problems occurring when multiple RI updates have to be)
Previous Message Tom Lane 2007-08-17 17:14:21 Re: tsearch2 in PostgreSQL 8.3?