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 ; [email protected] 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 中川 誠貴 <[email protected]> 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" <[email protected]> Sent: Saturday, January 15, 2011 2:56 AM To: "中川 誠貴" <[email protected]> Cc: <[email protected]> Subject: Re: [SQL] why does seq scan instead of index scan =?iso-2022-jp?B?GyRCQ2ZAbiEhQD81LhsoQg==?= <[email protected]> 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql -- Sent via pgsql-sql mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql -- // Dmitriy.
