From: Stuart Grimshaw <stuart@smgsystems.co.uk>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-sql@postgresql.org
Subject: Re: Why would this slow the query down so much?
Date: Tue, 16 Oct 2001 17:58:32 +0100
Message-ID: <E15tXY1-0005ZQ-00@garner.smgsystems.co.uk> (raw)
In-Reply-To: <14373.1003158756@sss.pgh.pa.us>
References: <xgXw7.2205$uU2.85101@wards>
<14373.1003158756@sss.pgh.pa.us>
On Monday 15 October 2001 16:12 pm, Tom Lane wrote:
> Stuart Grimshaw <nospam@smgsystems.co.uk> 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?
There are 194 rows in caturljoin where url = 93, 29806 rows in stories will
match those 194 rows and only 1 row in urllist will match.
--
| Stuart Grimshaw <stuart@footballnet.com>
| Chief Operations Officer
| Football Networks Ltd
|-
| t:07976 625221
| f:0870 7060260
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: stuart@smgsystems.co.uk, tgl@sss.pgh.pa.us
Subject: Re: Why would this slow the query down so much?
In-Reply-To: <E15tXY1-0005ZQ-00@garner.smgsystems.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox