X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 55A79D1CACC for ; Thu, 5 Feb 2004 06:32:39 +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 31766-05 for ; Thu, 5 Feb 2004 02:32:42 -0400 (AST) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id 32C83D1C7F0 for ; Thu, 5 Feb 2004 02:32:35 -0400 (AST) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id i156WSY04174; Thu, 5 Feb 2004 15:32:28 +0900 Message-ID: <006401c3ebb1$d4237c60$7201a8c0@mst1x5r347kymb> From: "Iain" To: "'Edoardo Ceccarelli'" Cc: References: <2s28b9$kqpmo@mailr-1.tiscali.it> Subject: Re: R: slow seqscan after vacuum analize Date: Thu, 5 Feb 2004 15:32:29 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/53 X-Sequence-Number: 12227 > Yes, you are right but it wasn't the case this time, I have run the explain plenty of > times with same results. I think that the reason was that I made a simple VACUUM, > after a VACUUM FULL ANALYZE (1h!!) things are ok It's reasonable to expect that a seq scan will perform faster after a full vacuum, as the physical size and organization of the table has been changed. I wouldn't expact a plain vacuum to have any tangible affect on performance, for the better or for the worse.. I'd like to know more about the possibility of plain vacuums harming performance. This is the first I've heard of it. Vacuum full is not always an option in a production environment.