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 591DE30FF81 for ; Thu, 26 Jun 2003 16:04:13 +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 75024-08 for ; Thu, 26 Jun 2003 13:04:03 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 7C22430FF88 for ; Thu, 26 Jun 2003 13:04:02 -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 h5QG3qQQ025815; Thu, 26 Jun 2003 12:03:52 -0400 (EDT) To: Manfred Koizar Cc: Andre Schubert , pgsql-performance@postgresql.org Subject: Re: problem with pg_statistics In-reply-to: References: <20030626151515.5fd0faf0.andre@km3.de> <24083.1056636485@sss.pgh.pa.us> Comments: In-reply-to Manfred Koizar message dated "Thu, 26 Jun 2003 17:51:56 +0200" Date: Thu, 26 Jun 2003 12:03:52 -0400 Message-ID: <25814.1056643432@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/182 X-Sequence-Number: 2266 Manfred Koizar writes: > On Thu, 26 Jun 2003 10:08:05 -0400, Tom Lane > wrote: >> Try reducing random_page_cost > With index scan cost being more than 25 * seq scan cost, I guess that > - all other things held equal - even random_page_cost = 1 wouldn't > help. Oh, you're right, I was comparing the wrong estimated costs. Yeah, changing random_page_cost won't fix it. > Or there's something wrong with correlation? That seems like a good bet. Andre, is this table likely to be physically ordered by time_stamp, or nearly so? If so, do you expect that condition to persist, or is it just an artifact of a test setup? regards, tom lane