X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id AAD81D1B507 for ; Mon, 29 Sep 2003 02:29:38 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 76970-07 for ; Sun, 28 Sep 2003 23:29:31 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 6E378D1B4F1 for ; Sun, 28 Sep 2003 23:29:27 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3692966; Sun, 28 Sep 2003 19:30:03 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Palle Girgensohn , pgsql-performance@postgresql.org Subject: Re: avoiding seqscan? Date: Sun, 28 Sep 2003 19:28:52 -0700 User-Agent: KMail/1.4.3 References: <95900000.1064782481@palle.girgensohn.se> <200309281434.25881.josh@agliodbs.com> <161280000.1064789814@palle.girgensohn.se> In-Reply-To: <161280000.1064789814@palle.girgensohn.se> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200309281928.52113.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/350 X-Sequence-Number: 3716 Palle, > Indeed, setting random_page_cost does the trick. Thanks! > > It seems to make sense to set random_page_cost to this value. Are there any > drawbacks? Only if your server was heavily multi-tasking, and as a result had little RAM+CPU available. Then you'd want to raise the value again. -- Josh Berkus Aglio Database Solutions San Francisco