X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6B59E5639E for ; Mon, 14 Mar 2005 06:29:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 94618-04 for ; Mon, 14 Mar 2005 06:29:06 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0E9A055F4A for ; Mon, 14 Mar 2005 06:29:05 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2E6T6iK005581; Mon, 14 Mar 2005 01:29:06 -0500 (EST) To: Daniel Schuchardt Cc: pgsql-performance@postgresql.org Subject: Re: cpu_tuple_cost In-reply-to: References: Comments: In-reply-to Daniel Schuchardt message dated "Fri, 11 Mar 2005 15:25:29 +0100" Date: Mon, 14 Mar 2005 01:29:06 -0500 Message-ID: <5580.1110781746@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/243 X-Sequence-Number: 10948 Daniel Schuchardt 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