Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 8ADC62E3801 for ; Wed, 23 Jan 2008 04:47:51 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 52866-05 for ; Wed, 23 Jan 2008 04:47:46 -0400 (AST) Received: from mail.mnc.ch (62-2-77-205.static.cablecom.ch [62.2.77.205]) by postgresql.org (Postfix) with ESMTP id 0A6C02E3663 for ; Wed, 23 Jan 2008 04:47:46 -0400 (AST) Received: from localhost (mail2.mnc.ch [127.0.0.1]) by mail.mnc.ch (Postfix) with ESMTP id B10322308B; Wed, 23 Jan 2008 08:48:30 +0000 (GMT) X-Virus-Scanned: amavisd-new at mnc.ch Received: from mail.mnc.ch ([127.0.0.1]) by localhost (mail2.mnc.ch [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 2m-HQ5G8Paw1; Wed, 23 Jan 2008 08:48:29 +0000 (GMT) Received: from meuh.localdomain (62-2-77-204.static.cablecom.ch [62.2.77.204]) by mail.mnc.ch (Postfix) with ESMTP id D735E23089; Wed, 23 Jan 2008 08:48:29 +0000 (GMT) Received: by meuh.localdomain (Postfix, from userid 1000) id 33C1E183733; Wed, 23 Jan 2008 09:47:42 +0100 (CET) To: "Luiz K. Matsumura" Cc: pgsql-performance@postgresql.org Subject: Re: SELECT * FROM table is too slow References: <47656FC5.8060102@wooh.hu> <47657068.5070200@commandprompt.com> <479647A1.6010101@planit.com.br> From: Guillaume Cottenceau X-Hashcash: 1:20:080123:luiz@planit.com.br::XXuBPpDrtWpFJkPU:0000000000000000000000000000000000000000000JhWo X-Hashcash: 1:20:080123:pgsql-performance@postgresql.org::siTbTW/lC/jB1wBm:000000000000000000000000000000B0j Date: Wed, 23 Jan 2008 09:47:42 +0100 In-Reply-To: <479647A1.6010101@planit.com.br> (Luiz K. Matsumura's message of "Tue\, 22 Jan 2008 17\:44\:33 -0200") Message-ID: <877ii1ylld.fsf@mnc.ch> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/189 X-Sequence-Number: 28428 "Luiz K. Matsumura" writes: > If we run the commands "vacumm full analyze" If you're using the cost based vacuum delay, don't forget that it will probably take long; possibly, you may deactivate it locally before running VACUUM FULL, in case the locked table is mandatory for your running application(s). -- Guillaume Cottenceau, MNC Mobile News Channel SA