Re: Limit clause not using index
От | John A Meinel |
---|---|
Тема | Re: Limit clause not using index |
Дата | |
Msg-id | 42B8275C.8040300@arbash-meinel.com обсуждение исходный текст |
Ответ на | Limit clause not using index (Yves Vindevogel <yves.vindevogel@implements.be>) |
Ответы |
Re: Limit clause not using index
|
Список | pgsql-performance |
Yves Vindevogel wrote: > Hi, > > I have a very simple query on a big table. When I issue a "limit" > and/or "offset" clause, the query is not using the index. > Can anyone explain me this ? You didn't give enough information. What does you index look like that you are expecting it to use? Generally, you want to have matching columns. So you would want CREATE INDEX blah ON tblprintjobs(loginuser, desceventdate, desceventtime); Next, you should post EXPLAIN ANALYZE instead of regular explain, so we can have an idea if the planner is actually making correct estimations. John =:-> > > rvponp=# explain select * from tblprintjobs order by loginuser, > desceventdate, desceventtime offset 25 limit 25 ; > QUERY PLAN > ----------------------------------------------------------------------------------- > > Limit (cost=349860.62..349860.68 rows=25 width=206) > -> Sort (cost=349860.56..351416.15 rows=622236 width=206) > Sort Key: loginuser, desceventdate, desceventtime > -> Seq Scan on tblprintjobs (cost=0.00..25589.36 rows=622236 width=206) > (4 rows) > > rvponp=# explain select * from tblprintjobs order by loginuser, > desceventdate, desceventtime ; > QUERY PLAN > ----------------------------------------------------------------------------- > > Sort (cost=349860.56..351416.15 rows=622236 width=206) > Sort Key: loginuser, desceventdate, desceventtime > -> Seq Scan on tblprintjobs (cost=0.00..25589.36 rows=622236 width=206) > (3 rows) > > Met vriendelijke groeten, > Bien à vous, > Kind regards, > > *Yves Vindevogel* > *Implements*
Вложения
В списке pgsql-performance по дате отправления: