pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Schuchardt <daniel_schuchardt@web.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: cpu_tuple_cost
Date: Mon, 14 Mar 2005 01:29:06 -0500
Message-ID: <5580.1110781746@sss.pgh.pa.us> (raw)
In-Reply-To: <d0s9o7$1da1$1@news.hub.org>
References: <d0s9o7$1da1$1@news.hub.org>

Daniel Schuchardt <daniel_schuchardt@web.de> writes:
> i have a query plan who is bad with standard cpu_tuple_costs and good if 
> I raise cpu_tuple_costs. Is it is a good practice to raise them if i 
> want to force postgres to use indexes more often?

Reducing random_page_cost is usually the best way to get the planner to
favor indexscans more.

			regards, tom lane



view thread (20+ messages)  latest in thread

Message-ID: <5580.1110781746@sss.pgh.pa.us>
Permalink:  ../5580.1110781746@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5580.1110781746@sss.pgh.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: tgl@sss.pgh.pa.us, daniel_schuchardt@web.de
  Subject: Re: cpu_tuple_cost
  In-Reply-To: <5580.1110781746@sss.pgh.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