Re: random_page_cost = 2.0 on Heroku Postgres

On Fri, Feb 10, 2012 at 11:32 AM, Josh Berkus <josh@agliodbs.com> wrote:
> On 2/9/12 2:41 PM, Peter van Hardenberg wrote:
> So one thought would be to add in pg_stat_statements to your platform
> ... something I'd like to see Heroku do anyway.  Then you can sample
> this across dozens (or hundreds) of user databases, each with RPC set to
> a slightly different level, and aggregate it into a heat map.
>

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.

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.

--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut