Postgres Pro
Downloads
Home   >   mailing lists

*_cost recommendation with 8.3 and a fully cached db - Mailing list pgsql-performance

From Guillaume Smet
Subject *_cost recommendation with 8.3 and a fully cached db
Date
Msg-id 1d4e0c10801230436o7165a7fap760b36a5ff9ef0e8@mail.gmail.com
Whole thread Raw
List pgsql-performance
Tree view 
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

pgsql-performance by date:

Previous
From: "Guillaume Smet"
Date:
Subject: Re: Workaround for cross column stats dependency
Next
From: "Dmitry Potapov"
Date:
Subject: planner chooses unoptimal plan on joins with complex key