Re: Improving N-Distinct estimation by ANALYZE

Поиск
Список
Период
Сортировка
Искать
От
Simon Riggs
Тема
Re: Improving N-Distinct estimation by ANALYZE
Дата
Msg-id
1136925258.21025.433.camel@localhost.localdomain
Ответ на
Список
Дерево обсуждения
Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Trent Shipley <tshipley@deru.com>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Rod Taylor <pg@rbt.ca>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE "Jim C. Nasby" <jnasby@pervasive.com>
Re: Improving N-Distinct estimation by ANALYZE "Jim C. Nasby" <jnasby@pervasive.com>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE "Jim C. Nasby" <jnasby@pervasive.com>
Re: Improving N-Distinct estimation by ANALYZE Tom Lane <tgl@sss.pgh.pa.us>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Lukas Smith <smith@pooteeweet.org>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE "Jim C. Nasby" <jnasby@pervasive.com>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Tom Lane <tgl@sss.pgh.pa.us>
Re: Improving N-Distinct estimation by ANALYZE "Jim C. Nasby" <jnasby@pervasive.com>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Tom Lane <tgl@sss.pgh.pa.us>
Re: Improving N-Distinct estimation by ANALYZE Manfred Koizar <mkoi-pg@aon.at>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Kenneth Marshall <ktm@it.is.rice.edu>
Re: Improving N-Distinct estimation by ANALYZE Tom Lane <tgl@sss.pgh.pa.us>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
Re: Improving N-Distinct estimation by ANALYZE Josh Berkus <josh@agliodbs.com>
Re: Improving N-Distinct estimation by ANALYZE Greg Stark <gsstark@mit.edu>
Re: Improving N-Distinct estimation by ANALYZE Simon Riggs <simon@2ndquadrant.com>
On Mon, 2006-01-09 at 22:08 -0500, Greg Stark wrote:

> So it's not the 8k block reading that's fooling Linux into reading ahead 32k.
> It seems 32k readahead is the default for Linux, or perhaps it's the
> sequential access pattern that's triggering it.

Nah, Linux 2.6 uses flexible readahead logic. It increases slowly when
you read sequentially, but halves the readahead if you do another access
type. Can't see that would give an average readahead size of 32k.

Anyway.... this is one just reason for change...

Best Regards, Simon Riggs


В списке pgsql-hackers по дате отправления
От: Harald Fuchs
Дата:
От: Dave Page
Дата:
FAQ