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 414BAD1B49E for ; Thu, 5 Feb 2004 02:21:13 +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 60341-04 for ; Wed, 4 Feb 2004 22:21:12 -0400 (AST) Received: from mailr-1.tiscali.it (mailr-1.tiscali.it [212.123.84.81]) by svr1.postgresql.org (Postfix) with ESMTP id A6EECD1D278 for ; Wed, 4 Feb 2004 22:21:09 -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 03:21:14 +0100 Message-Id: <2s28b9$kqpmo@mailr-1.tiscali.it> X-BrightmailFiltered: true Reply-To: From: "Edoardo Ceccarelli" To: "'David F. Skoll'" , "'Edoardo Ceccarelli'" Cc: Subject: R: R: slow seqscan after vacuum analize Date: Thu, 5 Feb 2004 03:18:31 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcPrjiOArmfTV957Sf6FQqNhWE7CkQAAB3xg 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/52 X-Sequence-Number: 12226 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 V= ACUUM, after a VACUUM FULL ANALYZE (1h!!) things are ok=20 Best Regards Edoardo > -----Messaggio originale----- > Da: David F. Skoll [mailto:dfs@roaringpenguin.com]=20 > Inviato: gioved=EC 5 febbraio 2004 3.17 > A: Edoardo Ceccarelli > Cc: pgsql-admin@postgresql.org > Oggetto: Re: R: [ADMIN] slow seqscan after vacuum analize >=20 > On Thu, 5 Feb 2004, Edoardo Ceccarelli wrote: >=20 > > Things are worst only for seqscan, when it uses indexscan=20 > timing is good. >=20 > It might just be that running VACUUM flushed the operating=20 > system's buffer cache. >=20 > I always try running two or three EXPLAIN ANALYZE's in a row=20 > for the same query. Usually, the first one takes much longer=20 > than the rest. >=20 > Regards, >=20 > David. >=20 >=20