I see why it would now. But it would be nice if the message mentioned
the root cause of the problem - that the tsquery value does not contain
any lexemes and thus is not valid for doing a search.
... doing a index search :(. GIN core doesn't know anything about
tsvector/tsquery/tsearch - so,
Thanks for the clarification Teodor - it makes much more sense now.
I'd agree the error message is confusing, particularly since this works:
set enable_seqscan to on;
set enable_indexscan to off;
set enable_bitmapscan to off;
select *
from test.features
where to_tsquery('') @@ features.vector;
explain analyze
select *
from test.features
where to_tsquery('') @@ features.vector
ERROR: Gin doesn't support full scan due to it's awful inefficiency
Look:
contrib_regression=# select '{1,2,3}'::int4[] @ '{}'; --contains
?column?
--
t
(1 row)
contrib_regression=# select '{1,2,3}'
Hi Tom,
Thanks for the quick reply.
>> Sorry, mistyped the query causing the problem. It is:
>
>> select *
>> from maps, features
>> where maps.query @@ features.tags_vector;
>
> In that case it's fair to ask what query values you have stored in maps.
> In particular I imagine that you'll find
Charlie Savage <[EMAIL PROTECTED]> writes:
> Sorry, mistyped the query causing the problem. It is:
> select *
> from maps, features
> where maps.query @@ features.tags_vector;
In that case it's fair to ask what query values you have stored in maps.
In particular I imagine that you'll find that a
Sorry, mistyped the query causing the problem. It is:
select *
from maps, features
where maps.query @@ features.tags_vector;
Thanks,
Charlie
Charlie Savage wrote:
I've run across another GIN index issue - using postgresql 8.1.4 on
Window/Linux with the GIN/tsearch2 patch.
I have two tabl
I've run across another GIN index issue - using postgresql 8.1.4 on
Window/Linux with the GIN/tsearch2 patch.
I have two tables like this:
CREATE TABLE maps
(
id serial,
query tsearch2.tsquery
)
CREATE TABLE features
(
id serial,
vector tsearch2.tsvector
)
CREATE INDEX idx_features_t
