X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 70173D1B4B1 for ; Tue, 2 Dec 2003 00:45:57 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 20740-10 for ; Mon, 1 Dec 2003 20:45:31 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 67E86D1B44D for ; Mon, 1 Dec 2003 20:45:28 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hB20jT19008533; Mon, 1 Dec 2003 19:45:30 -0500 (EST) To: Jared Carr Cc: pgsql-performance@postgresql.org Subject: Re: A question on the query planner In-reply-to: <3FCBB639.10409@89glass.com> References: <3FCBB639.10409@89glass.com> Comments: In-reply-to Jared Carr message dated "Mon, 01 Dec 2003 13:44:25 -0800" Date: Mon, 01 Dec 2003 19:45:29 -0500 Message-ID: <8532.1070325929@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/21 X-Sequence-Number: 4881 Jared Carr writes: > I am currently working on optimizing some fairly time consuming queries > on a decently large dataset. It doesn't look that large from here ;-). I'd suggest experimenting with reducing random_page_cost, since at least for your test query it sure looks like everything is in RAM. In theory random_page_cost = 1.0 is the correct setting for all-in-RAM cases. regards, tom lane