Received: from mail1.hub.org (webmail.hub.org [216.126.85.1]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9FNbmP72999 for ; Mon, 15 Oct 2001 19:37:48 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us ([192.204.191.242]) by mail1.hub.org (8.11.3/8.11.4) with ESMTP id f9FFCeX35282 for ; Mon, 15 Oct 2001 11:12:40 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f9FFCac14376 for ; Mon, 15 Oct 2001 11:12:37 -0400 (EDT) To: pgsql-sql@postgresql.org Subject: Re: Why would this slow the query down so much? In-reply-to: References: Comments: In-reply-to Stuart Grimshaw message dated "Wed, 10 Oct 2001 13:35:27 +0100" Date: Mon, 15 Oct 2001 11:12:36 -0400 Message-ID: <14373.1003158756@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/189 X-Sequence-Number: 5144 Stuart Grimshaw writes: > SELECT a.category, b.headline, b.added, c.friendlyname > FROM caturljoin as a > INNER JOIN stories as b ON (a.url = b.source) > INNER JOIN urllist as c ON (a.url = d.urn) > WHERE a.category = 93 ORDER BY b.added DESC LIMIT 1; (I assume "d.urn" is a typo for "c.urn"...) The query plan you show looks pretty reasonable if the planner's row count estimates are in the right ballpark. How many caturljoin rows have category = 93? How many stories rows will match each caturljoin row? How many urllist rows ditto? regards, tom lane