Received: from mail1.hub.org (webmail.hub.org [216.126.85.1]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9FNaUP72425 for ; Mon, 15 Oct 2001 19:36:30 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by mail1.hub.org (8.11.3/8.11.4) with ESMTP id f9FGtXX60381 for ; Mon, 15 Oct 2001 12:55:33 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 147949; Mon, 15 Oct 2001 09:55:30 -0700 From: "Josh Berkus" Subject: Re: Why would this slow the query down so much? To: Stuart Grimshaw , pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 15 Oct 2001 09:55:30 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200110/198 X-Sequence-Number: 5153 Stuart, > ------------------------------------------ > 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; > ------------------------------------------ Hmmm? Where did table "d" come from? If this is really your query, that's your problem. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco