Re: random_page_cost = 2.0 on Heroku Postgres

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Peter van Hardenberg <pvh(at)pvh(dot)ca>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: random_page_cost = 2.0 on Heroku Postgres
Date: 2012-02-11 01:40:32
Message-ID: 4F35C710.1030507@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Peter van Hardenberg 2012-02-11 02:13:07 Re: random_page_cost = 2.0 on Heroku Postgres
Previous Message Peter van Hardenberg 2012-02-10 21:30:58 Re: random_page_cost = 2.0 on Heroku Postgres