Re: Why would this slow the query down so much?

From: Stuart Grimshaw <stuart(at)smgsystems(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Why would this slow the query down so much?
Date: 2001-10-16 16:58:32
Message-ID: E15tXY1-0005ZQ-00@garner.smgsystems.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Monday 15 October 2001 16:12 pm, Tom Lane wrote:
> Stuart Grimshaw <nospam(at)smgsystems(dot)co(dot)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(at)footballnet(dot)com>
| Chief Operations Officer
| Football Networks Ltd
|-
| t:07976 625221
| f:0870 7060260

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Anthony Bouvier 2001-10-16 18:23:43 Multiple Parameters to an Aggregate Function
Previous Message Haller Christoph 2001-10-16 16:45:27 Deleting obsolete values