Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 8F1D62E0099 for ; Mon, 26 May 2008 20:57:40 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 50157-06 for ; Mon, 26 May 2008 20:57:03 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by developer.postgresql.org (Postfix) with ESMTP id CB6B12E0070 for ; Mon, 26 May 2008 20:57:07 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n4so2368579wag.5 for ; Mon, 26 May 2008 16:57:06 -0700 (PDT) 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=IWjd1HR3dkk8tj4Ayb0CnLyYoT/FCwd375oDh/Dq8Cg=; b=m+hzOq9dZuic7Hz0nVtEJF3/6n8lHk0qvBtgWUgApRB5MemxtZnFBM8N6w7HeWT44/lK3GMqo7AjzALSQi8Ej5N994Fk6qOf18X5jZNdhdOd3cfAJZZd7ck7pK22RzaI1pad2diahrdI6cJUIEaYvsStpoTrMoFVIeRk+/9Cj8g= 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=WdSN2oooziqVKNYtUQzNcqBUPwKira+QKDklhjhaxXfNzjRrMqhONFo6HGy17ehmaHPDAg8eZUu1ymDVHzUEyRRjuR+MDybe5cHzpp/y3W+ekHSSOeVLzIB/wwdx6MpcRnMxtWYAhW6nFcwG0y8aV0xUTlt6nweXv9lfzarPdj8= Received: by 10.114.184.9 with SMTP id h9mr628484waf.151.1211846226410; Mon, 26 May 2008 16:57:06 -0700 (PDT) Received: by 10.114.56.5 with HTTP; Mon, 26 May 2008 16:57:06 -0700 (PDT) Message-ID: <82fa9e310805261657u4a84b5fftd3abb50314f18815@mail.gmail.com> Date: Mon, 26 May 2008 16:57:06 -0700 From: mark To: Justin Subject: Re: select query takes 13 seconds to run with index Cc: pgsql-general@postgresql.org, pgsql-performance@postgresql.org In-Reply-To: <483B4C74.7000703@emproshunts.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <82fa9e310805261549m2362fbe8sbf18789938fee833@mail.gmail.com> <483B4729.7050402@emproshunts.com> <82fa9e310805261632y46f306fdh84e2da62ffbd7873@mail.gmail.com> <483B4C74.7000703@emproshunts.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/955 X-Sequence-Number: 133354 On Mon, May 26, 2008 at 4:49 PM, Justin wrote: > mark wrote: > > On Mon, May 26, 2008 at 4:26 PM, Justin wrote: > mark wrote: > Hi, is there anyway this can be made faster? id is the primary key, > and there is an index on uid.. > thanks > EXPLAIN ANALYZE select * from pokes where uid = 578439028 order by id > DESC limit 6; > QUERY > PLAN > > ---------------------------------------------------------------------------------------------------------------------------------------------------- > Limit (cost=0.00..9329.02 rows=6 width=135) (actual > time=13612.247..13612.247 rows=0 loops=1) > -> Index Scan Backward using pokes_pkey on pokes > (cost=0.00..5182270.69 rows=3333 width=135) (actual > time=13612.245..13612.245 rows=0 loops=1) > Filter: (uid = 578439028) > Total runtime: 13612.369 ms > (4 rows) > > > First this should be posted on performance list. > > > sorry about this. > > > > how many records are in this table? > > > 22334262, 22 million records. > > > > The estimate is way off, when was the last time Vaccum was on the table? > > > about a week ago i ran this VACUUM VERBOSE ANALYZE; > this table is never updated or deleted, rows are just inserted... > > > > > What verison of Postgresql are you running > > > 8.3.1 > > > > Size of the Table > > > 22 million rows approximately > > > I have no experience on large datasets so people with more experience in > this area are going to have to chime in. > My gut feel is 13 seconds for Postgresql to sort through an index of that > size and table is not bad. > > you may need to take a look at hardware and postgresql.config settings to > improve the performance for this query > > This query is very simple where changing it around or adding index results > massive improvements is not going to help in this case. the hardware is e5405 dual quad core on a 16GB RAM machine, with 8.3.1 default settings except maximum connections increased...