Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id DB4E4477423 for ; Wed, 15 Jan 2003 15:37:16 -0500 (EST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id C068A477240 for ; Wed, 15 Jan 2003 14:44:01 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id DE0EDD60D; Wed, 15 Jan 2003 11:44:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id D3D555C02; Wed, 15 Jan 2003 11:44:01 -0800 (PST) Date: Wed, 15 Jan 2003 11:44:01 -0800 (PST) From: Stephan Szabo To: Roman Fail Cc: Subject: Re: 7.3.1 New install, large queries are slow In-Reply-To: <9B1C77393DED0D4B9DAA1AA1742942DA0E4BF9@pos_pdc.posportal.com> Message-ID: <20030115113159.F91182-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/121 X-Sequence-Number: 768 On Wed, 15 Jan 2003, Roman Fail wrote: > The disks are not reading at max speed during the query - when I ran a > VACUUM ANALYZE (after data migration), sar -b was consistently 100,000 > block reads/sec. It does not seem like the hardware is holding back > things here. I read something about 'fsync' recently, would changing > that setting apply in this case? You ran vacuum analyze, but some of the explain still looks suspiciously like it's using default statistics (dr and cr for example, unless they really do have 1000 rows). What are the actual query and table definitions for the query?