Re: Optimizing No matching record Queries

From: "Stephen Denne" <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>
To: "Pallav Kalva" <pkalva(at)livedatagroup(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Optimizing No matching record Queries
Date: 2008-02-12 22:09:29
Message-ID: F0238EBA67824444BC1CB4700960CB4804A4F34F@dmpeints002.isotach.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Pallav Kalva asked
...
> and listing0_.fklistingsourceid=5525
...
> order by listing0_.entrydate desc limit 10;

> -> Index Scan Backward using idx_listing_entrydate on
> listing listing0_ (cost=0.00..781557.28 rows=5118 width=107) (actual
> time=2113544.412..2113544.412 rows=0 loops=1)
> Filter: (fklistingsourceid = 5525)

Would it help to have a combined index on fklistingsourceid, entrydate?

Regards,
Stephen Denne.

Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer focus, and courage. This email with any attachments is confidential and may be subject to legal privilege. If it is not intended for you please advise by reply immediately, destroy it and do not copy, disclose or use it in any way.

__________________________________________________________________
This email has been scanned by the DMZGlobal Business Quality
Electronic Messaging Suite.
Please see http://www.dmzglobal.com/services/bqem.htm for details.
__________________________________________________________________

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dean Gibson (DB Administrator) 2008-02-13 00:07:29 Re: Optimizing No matching record Queries
Previous Message Pallav Kalva 2008-02-12 21:35:40 Optimizing No matching record Queries