X-Original-To: pgsql-performance@postgresql.org Received: from localhost (unknown [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id 7A3499234EE for ; Wed, 21 May 2003 06:00:26 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 82276-01 for ; Wed, 21 May 2003 06:00:20 -0400 (EDT) Received: from mithi.com (unknown [219.65.91.97]) by developer.postgresql.org (Postfix) with SMTP id 9402E92335B for ; Wed, 21 May 2003 06:00:10 -0400 (EDT) Received: (qmail 31784 invoked by uid 0); 21 May 2003 09:57:48 -0000 Received: from unknown (HELO amol) (192.168.0.46) by 0 with SMTP; 21 May 2003 09:57:48 -0000 Message-ID: <000a01c31f81$fa45da70$2e00a8c0@amol> From: "amol" To: References: <20030515075032.B60859-100000@megazone23.bigpanda.com> <00a101c31ea1$19e03d80$2e00a8c0@amol> <29058.1053443906@sss.pgh.pa.us> Subject: Re: nested select query failing Date: Wed, 21 May 2003 15:46:00 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/207 X-Sequence-Number: 1986 Hi Tom, U are great. As you have said, one item was numeric and another serial integer ) so it was applying seq scan. Thank you very much for your help everybody. regards, Amol ----- Original Message ----- From: "Tom Lane" To: "amol" Cc: Sent: Tuesday, May 20, 2003 8:48 PM Subject: Re: [PERFORM] nested select query failing > "amol" writes: > > explain analyze select attached_info.id from attached_tag_list, > > attached_info > > where > > attached_tag_list.attached_tag = 265 > > and > > attached_tag_list.id = attached_info.id > > > NOTICE: QUERY PLAN: > > > Nested Loop (cost=0.00..165349.50 rows=114 width=16) (actual > > time=117.14..8994.60 rows=15 loops=1) > > -> Index Scan using ix_attached_tag_list_id on attached_tag_list > > (cost=0.00..111.13 rows=96 width=12) (actual time=0.12..0.66 rows=15 > > loops=1) > > -> Seq Scan on attached_info (cost=0.00..1211.53 rows=33553 width=4) > > (actual time=3.67..197.98 rows=33553 loops=15) > > Total runtime: 8994.92 msec > > > - I have already indexed attached_info on id using following query > > CREATE INDEX attached_info_Index_1 ON attached_info(id) ; > > Hm. I'd have expected an index scan too. Maybe the two id columns are > not of the same datatype? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > >