Re: default_text_search_config and expression indexes - Mailing list pgsql-hackers

From tomas@tuxteam.de
Subject Re: default_text_search_config and expression indexes
Date
Msg-id 20070809180418.GB32082@www.trapp.net
Whole thread Raw
In response to Re: default_text_search_config and expression indexes  (Oleg Bartunov <oleg@sai.msu.su>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Aug 09, 2007 at 02:03:13PM +0400, Oleg Bartunov wrote:
> On Thu, 9 Aug 2007, tomas@tuxteam.de wrote:
> 
> >Maybe I'm missing something [...]

> I'm tired to repeat - index itself doesn't know about configuration !
> It just index tsvector data type. tsvector in turn can be obtained
> using various ways:
> 1. manually
> 2. to_tsvector
> 
> tsvector can be stored in a separate attribute or be fully virtual
> like in expressional index.
> 
> Moreover, tsvector can be obtained using various configurations depending
> on your application.

Yep. I think I got that.

Now what will be the "normal" case for a new user?

* build an index with a virtual tsvector (using a configuration). Then I would expect the "index" to know the "whole"
functionto calculate its entries -- that would include the config used.
 
 This would be more "compatible" with the approach stated elsewhere to always mention explicitly the config.

* manually. Would a novice do that? Or is that advanced stuff?

Regards -- and sorry for my stupid questions :)

- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFGu1ciBcgs9XrR2kYRAnVqAJ9mSc463I44JxLLDPpUZ/JirUVH5ACeOhUr
2/4aXs0ukMnvP8YCq8pamwQ=
=IgfC
-----END PGP SIGNATURE-----



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: crypting prosrc in pg_proc
Next
From: Hans-Juergen Schoenig
Date:
Subject: Re: crypting prosrc in pg_proc