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 C7010D1D570 for ; Thu, 5 Feb 2004 01:09:36 +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 39565-03 for ; Wed, 4 Feb 2004 21:09:33 -0400 (AST) Received: from mailr-1.tiscali.it (mailr-1.tiscali.it [212.123.84.81]) by svr1.postgresql.org (Postfix) with ESMTP id 6DCB2D1D55F for ; Wed, 4 Feb 2004 21:09:31 -0400 (AST) Received: from ppp-82-84-56-186.cust-adsl.tiscali.it (HELO alphaville) (82.84.56.186) by mailr-1.tiscali.it with ESMTP; 05 Feb 2004 02:09:35 +0100 Message-Id: <2s28b9$kqljc@mailr-1.tiscali.it> X-BrightmailFiltered: true Reply-To: From: "Edoardo Ceccarelli" To: "'Sam Barnett-Cormack'" Cc: Subject: R: R: slow seqscan after vacuum analize Date: Thu, 5 Feb 2004 02:06:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcPrgvSwmYIpRE3nQSyLwSP3Z1fmgAAAFJ5g In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/50 X-Sequence-Number: 12224 > ---------------------------------------------------------------------- > > ---------------- > > -------------------- > > Seq Scan on utente (cost=0.00..92174.50 rows=3 width=724) (actual > > time=705.41..6458.19 rows=15 loops=1) > > Filter: (luogorilasciodoc = 'ciao'::bpchar) Total > runtime: 6458.29 > > msec > > (3 rows > > > > Things are worst only for seqscan, when it uses indexscan > timing is good. > > Only thing I can think of is if storage method had been > changed. Not sure if that would even affect it, or if it > could do that by itself. > Just brainstorming. > Do you know how can I check if the storage method has changed? I was thinking that the priority target of a vacuum operation is to reclaim disk space - this might imply that the performance are worst for a seqscan - maybe it's normal. Anyway, I am doing a VACUUM FULL ANALYZE right now to see if things get better. Thanks for you hints Edoardo