Re: Optimizing a query

From: Shaun Thomas <sthomas(at)optionshouse(dot)com>
To: Kai Sellgren <kaisellgren(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Optimizing a query
Date: 2013-12-19 17:53:55
Message-ID: 52B332B3.9050402@optionshouse.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 12/17/2013 08:48 PM, Kai Sellgren wrote:

This is your select:

> SELECT *
> FROM "Log"
> LEFT JOIN "NewsArticle" ON "NewsArticle".id = "Log"."targetId" AND
> "Log"."targetType" = 'NewsArticle'
> ORDER BY "Log"."createdAt" DESC
> LIMIT 10

This is your index:

> CREATE INDEX "Log_targetId_targetType_idx"
> ON "Log"
> USING btree
> ("targetId", "targetType" COLLATE pg_catalog."default");

Unfortunately, this won't help you. You are not matching on any IDs you
indexed, aside from joining against the article table. You have no WHERE
clause to restrict the data set, so it absolutely must read the entire
table to find the most recent records. Without an index on "createdAt",
how is it supposed to know what the ten most recent records are?

Add an index to the createdAt column:

CREATE INDEX idx_log_createdat ON "Log" (createdAt DESC);

Using that, it should get the ten most recent Log records almost
immediately, including associated article content.

--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas(at)optionshouse(dot)com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Shaun Thomas 2013-12-19 18:19:18 Re: slow query - will CLUSTER help?
Previous Message Shaun Thomas 2013-12-19 17:44:09 Re: Unexpected pgbench result