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 4CD5856713 for ; Tue, 15 Mar 2005 02:05:05 +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 43526-01 for ; Tue, 15 Mar 2005 02:05:02 +0000 (GMT) Received: from biglumber.com (biglumber.com [207.228.252.42]) by svr1.postgresql.org (Postfix) with SMTP id 2BC4C56602 for ; Tue, 15 Mar 2005 02:04:58 +0000 (GMT) Received: (qmail 20575 invoked from network); 15 Mar 2005 02:05:01 -0000 Received: from unknown (HELO localhost) (207.228.252.42) by 0 with SMTP; 15 Mar 2005 02:05:01 -0000 From: "Greg Sabino Mullane" To: pgsql-performance@postgresql.org Subject: Re: cpu_tuple_cost X-PGP-Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 X-Request-PGP: http://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 In-Reply-To: <5580.1110781746@sss.pgh.pa.us> Date: Tue, 15 Mar 2005 02:05:01 -0000 X-Mailer: JoyMail 1.48 Message-ID: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.164 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/289 X-Sequence-Number: 10994 -----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. - -- Greg Sabino Mullane greg@turnstep.com PGP Key: 0x14964AC8 200503140702 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFCNX2avJuQZxSWSsgRAk7QAJ4lye7pEcQIWMRV2fs15bHGY2zBbACeJtLC E/vUG/lagjcyWPt9gfngsn0= =CKIq -----END PGP SIGNATURE-----