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 F1D0ED1B80B for ; Thu, 5 Feb 2004 19:33:52 +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 46478-09 for ; Thu, 5 Feb 2004 15:33:51 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id C34A1D1C9DA for ; Thu, 5 Feb 2004 15:33:49 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i15JXk1W005733; Thu, 5 Feb 2004 14:33:46 -0500 (EST) To: eddy@axa.it Cc: "'Christopher Browne'" , pgsql-admin@postgresql.org Subject: Re: R: R: slow seqscan after vacuum analize In-reply-to: <2s28b9$l7fca@mailr-1.tiscali.it> References: <2s28b9$l7fca@mailr-1.tiscali.it> Comments: In-reply-to "Edoardo Ceccarelli" message dated "Thu, 05 Feb 2004 18:00:52 +0100" Date: Thu, 05 Feb 2004 14:33:45 -0500 Message-ID: <5732.1076009625@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/63 X-Sequence-Number: 12237 "Edoardo Ceccarelli" writes: > Given a query that HAS to be executed with a seqscan I have noticed an > increase in time comparing before and after the vacuum. This is really hard to believe --- I cannot think of any mechanism that would result in that effect. Unless the vacuum were flushing the kernel's disk cache, but the effects of that would only persist for one scan. You did say that the increased time is repeatable if you do multiple seqscans after the vacuum? regards, tom lane