Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 29E132E31E8 for ; Tue, 22 Jan 2008 15:49:52 -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 42760-01-5 for ; Tue, 22 Jan 2008 15:49:46 -0400 (AST) Received: from andromeda1.neonex.com.br (dns3.neonex.com.br [201.28.22.10]) by postgresql.org (Postfix) with ESMTP id 4A5002E3801 for ; Tue, 22 Jan 2008 15:44:38 -0400 (AST) Received: from [200.206.25.4] (helo=[127.0.0.1]) by andromeda1.neonex.com.br with esmtpa (Exim 4.63) (envelope-from ) id 1JHP2y-0005DW-Kr for pgsql-performance@postgresql.org; Tue, 22 Jan 2008 17:44:36 -0200 Message-ID: <479647A1.6010101@planit.com.br> Date: Tue, 22 Jan 2008 17:44:33 -0200 From: "Luiz K. Matsumura" Organization: Plan IT Tecnologia =?ISO-8859-1?Q?Inform=E1tica_Ltda=2E?= User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pgsql-performance@postgresql.org References: <47656FC5.8060102@wooh.hu> <47657068.5070200@commandprompt.com> In-Reply-To: <47657068.5070200@commandprompt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 080122-1, 01/22/2008), Outbound message X-Antivirus-Status: Clean X-SA-Exim-Connect-IP: 200.206.25.4 X-SA-Exim-Rcpt-To: pgsql-performance@postgresql.org Subject: Re: SELECT * FROM table is too slow X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/181 X-Sequence-Number: 28420 > Adam PAPAI wrote: >> Hi pgsql-performance, >> >> I've a problem with the select * on a small table. >> >> See below: >> >> >> x7=# SELECT count(idn) from megjelenesek; >> count >> ------- >> 162 >> (1 row) >> >> Why does it take cca 18-20 sec to get the results? >> Too many indexes? > > You likely have a huge amount of dead rows. Try dumping and restoring > the table and remember to run vacuum (or autovacuum) often. > > Sincerely, > > Joshua D. Drake wrote:Hi, If we run the commands "vacumm full analyze" and "reindex table", this can be considered as equivalent to making a dump / restore in this case ?