Re: More thoughts about planner's cost estimates

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: More thoughts about planner's cost estimates
Дата
Msg-id
10464.1149281016@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: More thoughts about planner's cost estimates Rod Taylor <pg@rbt.ca>
Re: More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: More thoughts about planner's cost estimates Mike Benoit <ipso@snappymail.ca>
Re: More thoughts about planner's cost estimates Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: More thoughts about planner's cost estimates Josh Berkus <josh@agliodbs.com>
Re: More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: More thoughts about planner's cost estimates "Jim C. Nasby" <jnasby@pervasive.com>
Re: More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: More thoughts about planner's cost estimates Nicolai Petri <nicolai@catpipe.net>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Josh Berkus <josh@agliodbs.com>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Josh Berkus <josh@agliodbs.com>
Re: More thoughts about planner's cost estimates Josh Berkus <josh@agliodbs.com>
Re: More thoughts about planner's cost estimates Kenneth Marshall <ktm@it.is.rice.edu>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates David Fetter <david@fetter.org>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Josh Berkus <josh@agliodbs.com>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Josh Berkus <josh@agliodbs.com>
Re: More thoughts about planner's cost estimates "Todd A. Cook" <tcook@blackducksoftware.com>
Re: More thoughts about planner's cost estimates Jim Nasby <jnasby@pervasive.com>
Re: More thoughts about planner's cost estimates Hannu Krosing <hannu@skype.net>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: More thoughts about planner's cost estimates Hannu Krosing <hannu@skype.net>
Re: More thoughts about planner's cost estimates Jim Nasby <jnasby@pervasive.com>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Hannu Krosing <hannu@skype.net>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Greg Stark <gsstark@mit.edu>
Re: More thoughts about planner's cost estimates Michael Dean <mdean@sourceview.com>
Re: More thoughts about planner's cost estimates David Fetter <david@fetter.org>
Re: More thoughts about planner's cost estimates "Jim C. Nasby" <jnasby@pervasive.com>
Re: More thoughts about planner's cost estimates Mark Kirkwood <markir@paradise.net.nz>
Re: More thoughts about planner's cost estimates Tom Lane <tgl@sss.pgh.pa.us>
Greg Stark  writes:
> And a 5% sample is a pretty big. In fact my tests earlier showed the i/o from
> 5% block sampling took just as long as reading all the blocks. Even if we
> figure out what's causing that (IMHO surprising) result and improve matters I
> would only expect it to be 3-4x faster than a full scan.

One way to reduce the I/O pain from extensive sampling would be to turn
VACUUM ANALYZE into a genuine combined operation instead of a mere
notational shorthand for two separate scans.

I'd still be worried about the CPU pain though.  ANALYZE can afford to
expend a pretty fair number of cycles per sampled tuple, but with a
whole-table sample that's going to add up.
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Michael Dean
Дата:
От: David Fetter
Дата:
FAQ