On Wed, Apr 13, 2011 at 4:32 PM, Kevin Grittner <kevin.gritt...@wicourts.gov> wrote: > If you model the costing to reflect the reality on your server, good > plans will be chosen.
Wouldn't it be "better" to derive those costs from actual performance data measured at runtime? Say, pg could measure random/seq page cost, *per tablespace* even. Has that been tried? -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance