Thank you very much.
I will try hstore columns.
Thanks.
From: Dmitriy Igrishin
Sent: Sunday, January 16, 2011 1:36 AM
To: 中川 誠貴
Cc: Tom Lane ; pgsql-sql@postgresql.org
Subject: Re: [SQL] why does seq scan instead of index scan
Hey,
To avoid creation of custom GiST-index you can use
-
> From: "Tom Lane"
> Sent: Saturday, January 15, 2011 2:56 AM
> To: "中川 誠貴"
> Cc:
> Subject: Re: [SQL] why does seq scan instead of index scan
>
>
> =?iso-2022-jp?B?GyRCQ2ZAbiEhQD81LhsoQg==?= writes:
>>
>>> I'm t
: Re: [SQL] why does seq scan instead of index scan
=?iso-2022-jp?B?GyRCQ2ZAbiEhQD81LhsoQg==?= writes:
I'm trying to use like 'xx%' search on Text[] column.
I thought it uses index scan. But actually it uses seq scan.
Why?
Those ANY expressions are not indexable.
regar
=?iso-2022-jp?B?GyRCQ2ZAbiEhQD81LhsoQg==?= writes:
> I'm trying to use like 'xx%' search on Text[] column.
> I thought it uses index scan. But actually it uses seq scan.
> Why?
Those ANY expressions are not indexable.
regards, tom lane
--
Sent via pgsql-sql mailing lis
Hello everyone.
I'm trying to use like 'xx%' search on Text[] column.
Here is the SQL.
Select * From table Where 'aa' <= ANY(keywords) and 'aa\uFFFD' >
ANY(keywords)
This looks like wooking as I intend.
But partially not working.
There is the explanation.
Explain Select * From table Wher
