Re: seq scan instead of index scan
От
Kevin Grittner
Тема
Re: seq scan instead of index scan
Дата
Msg-id
4B2A6A6A020000250002D750@gw.wicourts.gov
Ответ на
seq scan instead of index scan (Karl Larsson)
Список
Дерево обсуждения
seq scan instead of index scan Karl Larsson <karl.larsson47@gmail.com>
Re: seq scan instead of index scan "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: seq scan instead of index scan Greg Smith <greg@2ndquadrant.com>
Re: seq scan instead of index scan Tom Lane <tgl@sss.pgh.pa.us>
Re: seq scan instead of index scan Karl Larsson <karl.larsson47@gmail.com>
Re: seq scan instead of index scan Scott Marlowe <scott.marlowe@gmail.com>
Re: seq scan instead of index scan Scott Marlowe <scott.marlowe@gmail.com>
Re: seq scan instead of index scan Karl Larsson <karl.larsson47@gmail.com>
Re: seq scan instead of index scan Scott Marlowe <scott.marlowe@gmail.com>
Re: seq scan instead of index scan Karl Larsson <karl.larsson47@gmail.com>
Re: seq scan instead of index scan Scott Marlowe <scott.marlowe@gmail.com>
Karl Larsson wrote: > When I make a subquery Postgres don't care about my indexes and > makes a seq scan instead of a index scan. Why? > Total runtime: 0.133 ms Because it thinks that it's faster that way with the particular data you now have in your tables. With more data, it might think some other plan is faster. It's running in less than 1/7500 second -- how sure are you that it would be significantly faster another way? -Kevin
В списке pgsql-performance по дате отправления