X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 901F053F74 for ; Thu, 12 May 2005 15:45:47 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47728-03 for ; Thu, 12 May 2005 18:45:44 +0000 (GMT) Received: from mail.liquidcore.com (mail.liquidcore.net [68.17.96.60]) by svr1.postgresql.org (Postfix) with ESMTP id 1C29F53F70 for ; Thu, 12 May 2005 15:45:43 -0300 (ADT) Received: (from root@localhost) by mail.liquidcore.com (8.13.1/8.12.10) id j4CIjtSh003080; Thu, 12 May 2005 13:45:55 -0500 Received: from [192.168.0.81] (ppasalalinux.nqadmin.com [192.168.0.81]) by mail.liquidcore.com (8.13.1/8.12.10) with ESMTP id j4CIjstD003044; Thu, 12 May 2005 13:45:54 -0500 Message-ID: <4283A51D.2060207@nqadmin.com> Date: Thu, 12 May 2005 13:49:01 -0500 From: Prasanth Reply-To: dbadmin@nqadmin.com User-Agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: Query Plan - Index Scan & Seq Scan References: <428370AC.3070207@nqadmin.com> <886.1115910870@sss.pgh.pa.us> <428379E0.4010709@nqadmin.com> <2052.1115913920@sss.pgh.pa.us> <428381C3.80205@nqadmin.com> <6708.1115915406@sss.pgh.pa.us> In-Reply-To: <6708.1115915406@sss.pgh.pa.us> X-Enigmail-Version: 0.90.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-scanner: scanned for malicious content X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.051 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200505/164 X-Sequence-Number: 17593 Ok read about the indexes and type matches. So is this fixed in 8.0? Thanks, -Prasanth. Tom Lane wrote: > Prasanth 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 > >