Re: random_page_cost = 2.0 on Heroku Postgres

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Marcos Ortiz Valmaseda <mlortiz(at)uci(dot)cu>
Subject: Re: random_page_cost = 2.0 on Heroku Postgres
Date: 2012-02-09 04:39:50
Message-ID: 00198dd656e4228cb66aa53a68ca0e14@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

> You can execute several queries with the three different values provided
> by Scott and Josh.
> - SET random_page_cost = 2.0
> First execution of the queries with EXPLAIN ANALYZE
> - SET random_page_cost = 1.4
> Second execution of the queries with EXPLAIN ANALYZE
> - SET random_page_cost = 1.2
> Second execution of the queries with EXPLAIN ANALYZE

Well, such a tool would ideally be smarter than that, such that
you would run EXPLAIN and compare to the previous plan and
only run EXPLAIN ANALYZE if the plan changed. One could even
decrement rpc slowly and find out at one points it changes,
which would be more interesting than testing arbitrary numbers.
Would lead to some really sweet graphs as well. :)

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201202082338
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk8zTewACgkQvJuQZxSWSsiprACfTlYKiC4SS1UnERU+1N/2EGhJ
s9AAoIXLJk88hoNHEkWKhUTqikDBtC/B
=S65l
-----END PGP SIGNATURE-----

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Marcos Ortiz Valmaseda 2012-02-09 05:11:43 Re: random_page_cost = 2.0 on Heroku Postgres
Previous Message Scott Marlowe 2012-02-09 04:38:34 Re: random_page_cost = 2.0 on Heroku Postgres