Re: random_page_cost = 2.0 on Heroku Postgres
От | Peter van Hardenberg |
---|---|
Тема | Re: random_page_cost = 2.0 on Heroku Postgres |
Дата | |
Msg-id | CAAcg=kWoqJK8ULRebPr0Lh=apXpCrJytKX6ZPryO3aohDrp76A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: random_page_cost = 2.0 on Heroku Postgres (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-performance |
On Fri, Feb 10, 2012 at 5:40 PM, Josh Berkus <josh@agliodbs.com> wrote: > Peter, > >> We've funded some work by Peter Geoghegan to make pg_stat_statements >> more useful, but the patch is currently sitting in the commitfest in >> need of a champion. I'd very much like to see it landed. > > Ok, let me review it then ... > >> Between that work, 9.2, and Dimitri's extension whitelist module, >> pg_stat_statements should be usefully installable by everyone. We'd >> seriously consider installing it by default, but that would make us >> Not Vanilla, which is something we avoid very diligently. > > Bummer. You can get why this would be useful for autotuning, though, yes? > Absolutely! Everything we can do to better monitor users' database performance without interfering (unduly) with that performance or affecting their dump/restore cycle is very exciting for us. -- Peter van Hardenberg San Francisco, California "Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
В списке pgsql-performance по дате отправления: