pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Greg Sabino Mullane <greg@turnstep.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: cpu_tuple_cost
Date: Mon, 14 Mar 2005 21:17:52 -0500 (EST)
Message-ID: <200503150217.j2F2HqA01460@candle.pha.pa.us> (raw)
In-Reply-To: <def6f62ce9d501044843c654a94832ef@biglumber.com>

Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> > Reducing random_page_cost is usually the best way to get the
> > planner to favor indexscans more.
> 
> On that note, can I raise the idea again of dropping the default
> value for random_page_cost in postgresql.conf? I think 4 is too
> conservative in this day and age. Certainly the person who will
> be negatively impacted by a default drop of 4 to 3 will be the
> exception and not the rule.

Agreed.  I think we should reduce it at least to 3.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (20+ messages)  latest in thread

Message-ID: <200503150217.j2F2HqA01460@candle.pha.pa.us>
Permalink:  ../200503150217.j2F2HqA01460@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200503150217.j2F2HqA01460@candle.pha.pa.us

 · 

reply

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: pgman@candle.pha.pa.us, greg@turnstep.com
  Subject: Re: cpu_tuple_cost
  In-Reply-To: <200503150217.j2F2HqA01460@candle.pha.pa.us>

* 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