Horton

Re: tsearch2 in PostgreSQL 8.3?

Michael Paesold <mpaesold@gmx.at>

View thread View on postgr.es
From: Michael Paesold <mpaesold@gmx.at>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Mike Rylander <mrylander@gmail.com>, Alvaro Herrera <alvherre@commandprompt.com>, Heikki Linnakangas <heikki@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2007-08-16T09:14:11Z
Lists: pgsql-hackers 
Bruce Momjian wrote:
> Uh, how are we going to prevent the auto-casting to tsvector from using
> the default GUC config, e.g. CREATE INDEX i ON x USING GIN(col)?
> 
> This is where I started to see the need for education and error-prone
> nature of the default GUC just wasn't worth having it, though I know
> others disagree.

It can be removed quite easily. AFAIR, this "feature" was added on 
suggestion of Tom Lane. It was certainly only added in this 
tsearch-to-core release cycle, see here:

http://archives.postgresql.org/pgsql-hackers/2007-03/msg01384.php

Teodor Sigaev wrote:
 > 2) added operator class for text and varchar
 >    CREATE INDEX idxname ON tblname USING GIN ( textcolumn );

So just remove the operator class or don't specify it as default 
operator class for GIN, and the thing is gone. Perhaps there is a better 
way to do this, though.

[...digging...] The idea was born in the thread starting here (involving 
Tom Lane, Joshua Drake, and Teodor Sigaev):
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00912.php
with the conclusion here:
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00936.php

Best Regards
Michael Paesold