Re: Query Plan - Index Scan & Seq Scan

From: Prasanth <dbadmin(at)nqadmin(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Query Plan - Index Scan & Seq Scan
Date: 2005-05-12 16:44:02
Message-ID: 428387D2.8050200@nqadmin.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thanks Tom.

Seems like having int2 after code is doing the trick.

Can you please explain the reasons behind this.

I Really appreciate your time.

Thanks,
-Prasanth.

Tom Lane wrote:
> Prasanth <dbadmin(at)nqadmin(dot)com> writes:
>
>>code data type is int2.
>
>
> Ah-hah. So "where code > 2::int2" should work noticeably better for
> you. Or you could do "where code > '2'" to avoid hard-wiring the data
> type knowledge into your queries. Or just change it to int4 ;-)
> Or update to 8.0.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Vishal Kashyap @ [SaiHertz] 2005-05-12 17:26:14 Compile Error for postgresql-8.0.3
Previous Message Prasanth 2005-05-12 16:41:05 Re: Query Plan - Index Scan & Seq Scan