Re: why does seq scan instead of index scan - Mailing list pgsql-sql

From 中川 誠貴
Subject Re: why does seq scan instead of index scan
Date
Msg-id 895509E8DA8F4649BBA565541CE333E9@IVPNAKAGAWAPC
Whole thread Raw
In response to Re: why does seq scan instead of index scan  (Dmitriy Igrishin <dmitigr@gmail.com>)
List pgsql-sql
Thank you very much.
 
I will try hstore columns.
 
Thanks.
 
 
 

Sent: Sunday, January 16, 2011 1:36 AM
Subject: Re: [SQL] why does seq scan instead of index scan

Hey,

To avoid creation of custom GiST-index you can use hstore,
which supports GiST and GIN indexes.
I propose you to add hstore column to the table and write trigger
function which will generate hstore from array on insert or update.
Or you can use hstore column instead of array.
Please, see http://www.postgresql.org/docs/9.0/static/hstore.html

2011/1/15 中川 誠貴 <nakagawa@ivp.co.jp>
Thank you for your response.

Are there any technique to index that query for like search on Text[] Columns?


Thanks.


Nakagawa Maskai


--------------------------------------------------
From: "Tom Lane" <tgl@sss.pgh.pa.us>
Sent: Saturday, January 15, 2011 2:56 AM
To: "中川 誠貴" <nakagawa@ivp.co.jp>
Cc: <pgsql-sql@postgresql.org>
Subject: Re: [SQL] why does seq scan instead of index scan


中川 誠貴 <nakagawa@ivp.co.jp> 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 list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql


--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql



--
// Dmitriy.


pgsql-sql by date:

Previous
From: Dmitriy Igrishin
Date:
Subject: Re: why does seq scan instead of index scan
Next
From: victor katemana
Date:
Subject: failing to connect to postgresql with php