From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tomáš Vondra <tv(at)fuzzy(dot)cz> |
Cc: | pgsql-bugs(at)postgresql(dot)org, craig(dot)macdonald(at)glasgow(dot)ac(dot)uk |
Subject: | Re: BUG #9038: trgm must have operand in index creation |
Date: | 2014-01-30 18:01:25 |
Message-ID: | 3022.1391104885@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
=?UTF-8?Q?Tom=C3=A1=C5=A1_Vondra?= <tv(at)fuzzy(dot)cz> writes:
> craig(dot)macdonald(at)glasgow(dot)ac(dot)uknapsal/a:
>> The documentation at
>> http://www.postgresql.org/docs/9.2/static/textsearch-indexes.html
>> is incorrect in the syntax of CREATE INDEX for GIN and GIST. According to
>> http://www.postgresql.org/docs/9.2/static/pgtrgm.html the keyword
>> gist_trgm_ops is also necessary:
> No it's not. The documentation about full-text clearly states that the column needs to be either tsvector or tsquery, but you're clearly using text.
Yeah, Tomas is right: section 12.9 is discussing the core full-text-search
datatypes, which have nothing much to do with contrib/pg_trgm's
facilities.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-01-30 18:41:54 | Re: BUG #9041: Strange error message with LATERAL and mixed WHERE/ON conditions |
Previous Message | Tomáš Vondra | 2014-01-30 15:34:39 | Re: BUG #9038: trgm must have operand in index creation |