Re: planning issue - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: planning issue
Date
Msg-id 45FAED51.8060705@commandprompt.com
Whole thread Raw
In response to planning issue  (Jonathan Vanasco <postgres@2xlp.com>)
Responses Re: planning issue  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-general
>
>         QUERY PLAN
>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Seq Scan on table_a  (cost=0.00..22779.68 rows=1 width=346)
>    Filter: ((id <> 10001) AND (((field_1)::text ~~* '123'::text) OR
> ((field_2)::text ~~* 'abc'::text)))
>
>
> however, i have the following indexes:
>
>     "table_a__pkey" PRIMARY KEY, btree (id)
>     "table_a__idx__field_1" btree (field_1)
>     "table_a__idx__field_2" btree (field_2)
>
> can anyone offer advice to help me use the indexes on this ?

create a function lower index and instead of calling ilike call ~
lower('123')

Joshua D. Drake



>
>
> // Jonathan Vanasco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


pgsql-general by date:

Previous
From: Jonathan Vanasco
Date:
Subject: planning issue
Next
From: Erik Jones
Date:
Subject: Re: PostgreSQL 8.2.3 VACUUM Timings/Performance