X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 31D8130FE16 for ; Thu, 26 Jun 2003 14:08:20 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 64541-04 for ; Thu, 26 Jun 2003 11:08:09 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id F2E5830FF5A for ; Thu, 26 Jun 2003 11:08:08 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h5QE86QQ024084; Thu, 26 Jun 2003 10:08:06 -0400 (EDT) To: Andre Schubert Cc: pgsql-performance@postgresql.org Subject: Re: problem with pg_statistics In-reply-to: <20030626151515.5fd0faf0.andre@km3.de> References: <20030626151515.5fd0faf0.andre@km3.de> Comments: In-reply-to Andre Schubert message dated "Thu, 26 Jun 2003 15:15:15 +0200" Date: Thu, 26 Jun 2003 10:08:05 -0400 Message-ID: <24083.1056636485@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/179 X-Sequence-Number: 2263 Andre Schubert writes: > i think i need a little help with a problem with pg_statistic. Try reducing random_page_cost --- although you'd be foolish to set it on the basis of just a single test query. Experiment with a few different tables, and keep in mind that repeated tests will be affected by caching. regards, tom lane