Re: Optimizing No matching record Queries
От | Stephen Denne |
---|---|
Тема | Re: Optimizing No matching record Queries |
Дата | |
Msg-id | F0238EBA67824444BC1CB4700960CB4804A4F34F@dmpeints002.isotach.com обсуждение исходный текст |
Ответ на | Optimizing No matching record Queries (Pallav Kalva <pkalva@livedatagroup.com>) |
Ответы |
Re: Optimizing No matching record Queries
|
Список | 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 attachmentsis 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. __________________________________________________________________
В списке pgsql-performance по дате отправления: