Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id UAA66751 for ; Wed, 12 May 1999 20:40:21 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id UAA03176; Wed, 12 May 1999 20:39:19 -0400 (EDT) To: gjerde@icebox.org cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] JOIN index/sequential select problem In-reply-to: Your message of Wed, 12 May 1999 18:00:24 -0500 (CDT) Date: Wed, 12 May 1999 20:39:18 -0400 Message-ID: <3174.926555958@sss.pgh.pa.us> From: Tom Lane gjerde@icebox.org writes: > Then postgres is not guessing right. Even tho the table only has > ~200 rows, the query still takes forever to finish. I have let it go for > a few minutes, and it still wasn't done.. Something wrong there; even with a nested loop, it shouldn't take more than a few seconds to process that query. Please dig into it a little more (do you have gprof?) and find where it's spending the time. regards, tom lane