Skip site navigation (1) Skip section navigation (2)

*_cost recommendation with 8.3 and a fully cached db

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: *_cost recommendation with 8.3 and a fully cached db
Date: 2008-01-23 12:36:44
Message-ID: 1d4e0c10801230436o7165a7fap760b36a5ff9ef0e8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hi Tom,

On May 9, 2007 6:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

Next:From: Dmitry PotapovDate: 2008-01-23 13:48:16
Subject: planner chooses unoptimal plan on joins with complex key
Previous:From: Guillaume SmetDate: 2008-01-23 09:05:53
Subject: Re: Workaround for cross column stats dependency

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group