X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 55CAED1B433 for ; Tue, 6 Jan 2004 21:42:12 +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 82664-08 for ; Tue, 6 Jan 2004 17:41:25 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id D80BBD1B4D4 for ; Tue, 6 Jan 2004 17:40:54 -0400 (AST) Received: from [63.195.55.98] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 4212926; Tue, 06 Jan 2004 13:41:55 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Michael Shapiro , pgsql-performance@postgresql.org Subject: Re: PgAdmin startup query VERY slow Date: Tue, 6 Jan 2004 13:17:30 -0800 User-Agent: KMail/1.4.3 References: <5.2.0.9.2.20040106144745.00bcfe30@pop.ncsa.uiuc.edu> <5.2.0.9.2.20040106152859.02a17ea8@pop.ncsa.uiuc.edu> In-Reply-To: <5.2.0.9.2.20040106152859.02a17ea8@pop.ncsa.uiuc.edu> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200401061317.30877.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/75 X-Sequence-Number: 5250 Mark, > That seemed to fix it. What does VACUUM ANALYZE do that VACUUM FULL does= =20 > not? What causes a database to need vacuuming? See the Online Docs: http://www.postgresql.org/docs/current/static/maintenance.html Incidentally, just ANALYZE would probably have fixed your problem. Please= do=20 suggest to the PGAdmin team that they add a FAQ item about this. --=20 -Josh Berkus Aglio Database Solutions San Francisco