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 37422D1B47E for ; Wed, 3 Dec 2003 23:22:52 +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 21780-07 for ; Wed, 3 Dec 2003 19:22:23 -0400 (AST) Received: from live (64-35-136-226.gohighspeed.com [64.35.136.226]) by svr1.postgresql.org (Postfix) with ESMTP id 2B7DAD1B446 for ; Wed, 3 Dec 2003 19:22:20 -0400 (AST) Received: from [192.168.254.101] (helo=89glass.com) by live with esmtp (Exim 3.35 #1 (Debian)) id 1ARgK1-0002hW-00; Wed, 03 Dec 2003 15:22:17 -0800 Message-ID: <3FCE700E.5070206@89glass.com> Date: Wed, 03 Dec 2003 15:21:50 -0800 From: Jared Carr User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg Stark Cc: Tom Lane , pgsql-performance@postgresql.org Subject: Re: A question on the query planner References: <3FCBB639.10409@89glass.com> <1070385381.24915.8650.camel@camel> <3FCCD225.8030609@89glass.com> <87d6b79har.fsf@stark.dyndns.tv> <3FCCE48B.10406@89glass.com> <871xrn9e09.fsf@stark.dyndns.tv> <3FCCF61E.90307@89glass.com> <87ptf697h0.fsf@stark.dyndns.tv> <25476.1070409047@sss.pgh.pa.us> <87znea7kis.fsf@stark.dyndns.tv> <26699.1070423607@sss.pgh.pa.us> <2704.1070473746@sss.pgh.pa.us> <3FCE2B08.6090606@89glass.com> <87k75d66jh.fsf@stark.dyndns.tv> In-Reply-To: <87k75d66jh.fsf@stark.dyndns.tv> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/61 X-Sequence-Number: 4921 Greg Stark wrote: >Jared Carr writes: > > > >>The patch definitely makes things more consistent...unfortunately it is more >>consistent toward the slower execution times. Of course I am looking at this >>simply from a straight performance standpoint and not a viewpoint of what >>*should* be happening. At any rate here are the query plans with the various >>settings. >> >> > >The optimizer seems to be at least considering reasonable plans now. It seems >from the estimates that you need to rerun analyze. You might try "vacuum full >analyze" to be sure. > >Also, you might try raising effective_cache_size and/or lowering >random_page_size (it looks like something around 2 might help). > > > Yep, I had forgotten to run vacuum since I had patched it :P. The overall performance is definitely better, I will go ahead and tweak the server settings and see what I can get. Thanks again for all the help.