Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E702C2E010C for ; Sun, 24 Feb 2008 20:27:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 81944-08 for ; Sun, 24 Feb 2008 20:27:50 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by postgresql.org (Postfix) with ESMTP id AA3482E00F9 for ; Sun, 24 Feb 2008 20:27:56 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so1580863waf.5 for ; Sun, 24 Feb 2008 16:27:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=qo+nSGHV/AWO+pU3uFOKfAV0j6fyXYkbQCPeRfDRkxo=; b=Fp7/87lpnRHyv1oUh0FLosDfR2kPYJcWi5/p4MsUOvvkBj44GSTfFNdldNt+2+xpsDoRpcRehMAJGMHn29AuQ5gur7o994hb+e62n5c010vNStDcZQwEqOVGfduwpGczri4qAtvYwGa9T5fdUP2SxyohYLgin4eIy6UDvVw2tMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dBfg2SDXRXxH3MKSPRMASJnWB6Z8YjVJJ1BZVfnsFWpA2a5FzmfR8rVja2t5hB8As2gwnpN3RSgrQ37D6oSUljt9Yjx4m7ciRF6mWLuuBrmT6IO66YW8S34+X5b/ujK4fZXHR+pBLIBg4C/KPw5rRAjazNh2o3BalNcpuQPcmGI= Received: by 10.115.46.9 with SMTP id y9mr2654340waj.129.1203899275358; Sun, 24 Feb 2008 16:27:55 -0800 (PST) Received: by 10.114.133.6 with HTTP; Sun, 24 Feb 2008 16:27:55 -0800 (PST) Message-ID: Date: Sun, 24 Feb 2008 18:27:55 -0600 From: "Scott Marlowe" To: "Sean Leach" Subject: Re: Weird issue with planner choosing seq scan Cc: "Stephen Denne" , pgsql-performance In-Reply-To: <1865C113-5FE9-4ED4-9472-EA6758D05FA3@wiggum.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5289.1203875431@sss.pgh.pa.us> <7ECB45D8-33ED-45FC-A0DA-D3DE25B6CC8E@wiggum.com> <6253.1203880225@sss.pgh.pa.us> <7EA909F9-92E9-4B36-9476-59A0A14A1F86@wiggum.com> <1865C113-5FE9-4ED4-9472-EA6758D05FA3@wiggum.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/313 X-Sequence-Number: 28855 On Sun, Feb 24, 2008 at 6:05 PM, Sean Leach wrote: > On Feb 24, 2008, at 4:03 PM, Scott Marlowe wrote: > > > > > What version pgsql is this? If it's pre 8.0 it might be worth looking > > into migrating for performance and maintenance reasons. > > It's the latest 8.3.0 release :( Urg. Then I wonder how your indexes are bloating but your table is not... you got autovac running? No weird lock issues? It's a side issue right now since the table is showing as non-bloated (unless you've got a long running transaction and that number is WAY off from your vacuum)