From: Guillaume Smet <guillaume.smet@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: *_cost recommendation with 8.3 and a fully cached db
Date: Wed, 23 Jan 2008 13:36:44 +0100
Message-ID: <1d4e0c10801230436o7165a7fap760b36a5ff9ef0e8@mail.gmail.com> (raw)
Hi Tom,
On May 9, 2007 6:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> To return to your original comment: if you're trying to model a
> situation with a fully cached database, I think it's sensible
> to set random_page_cost = seq_page_cost = 0.1 or so.
Is it still valid for 8.3 or is there any reason to change this
recommendation, considering the work you did on the planner during the
8.3 cycle?
Thanks.
--
Guillaume
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: guillaume.smet@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: *_cost recommendation with 8.3 and a fully cached db
In-Reply-To: <1d4e0c10801230436o7165a7fap760b36a5ff9ef0e8@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox