Re: random_page_cost = 2.0 on Heroku Postgres - Mailing list pgsql-performance

From Peter van Hardenberg
Subject Re: random_page_cost = 2.0 on Heroku Postgres
Date
Msg-id CAAcg=kWoqJK8ULRebPr0Lh=apXpCrJytKX6ZPryO3aohDrp76A@mail.gmail.com
Whole thread Raw
In response to Re: random_page_cost = 2.0 on Heroku Postgres  (Josh Berkus <josh@agliodbs.com>)
List 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 by date:

Previous
From: Josh Berkus
Date:
Subject: Re: random_page_cost = 2.0 on Heroku Postgres
Next
From: CSS
Date:
Subject: Re: rough benchmarks, sata vs. ssd