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 8B229D1B465 for ; Tue, 6 Jan 2004 21:33:19 +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 81670-08 for ; Tue, 6 Jan 2004 17:32:31 -0400 (AST) Received: from mail.ncsa.uiuc.edu (mail.ncsa.uiuc.edu [141.142.2.28]) by svr1.postgresql.org (Postfix) with ESMTP id 83C26D1C957 for ; Tue, 6 Jan 2004 17:31:28 -0400 (AST) X-Envelope-From: mshapiro@ncsa.edu X-Envelope-To: Received: from kalika.ncsa.edu (kalika.ncsa.uiuc.edu [141.142.97.63]) by mail.ncsa.uiuc.edu (8.11.6p2/8.11.6) with ESMTP id i06LVUC29113 for ; Tue, 6 Jan 2004 15:31:30 -0600 Message-Id: <5.2.0.9.2.20040106152859.02a17ea8@pop.ncsa.uiuc.edu> X-Sender: mshapiro@pop.ncsa.uiuc.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 06 Jan 2004 15:31:29 -0600 To: pgsql-performance@postgresql.org From: Michael Shapiro Subject: Re: PgAdmin startup query VERY slow In-Reply-To: <200401061301.43954.josh@agliodbs.com> References: <5.2.0.9.2.20040106144745.00bcfe30@pop.ncsa.uiuc.edu> <5.2.0.9.2.20040106144745.00bcfe30@pop.ncsa.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/74 X-Sequence-Number: 5249 That seemed to fix it. What does VACUUM ANALYZE do that VACUUM FULL does not? What causes a database to need vacuuming? At 01:01 PM 1/6/2004 -0800, Josh Berkus wrote: >Michael, > > > With a particular database, PgAdmin3 takes a very long time to connect > to a > > database. this is not a general problem with PgAdmin, but only with one > > database out of many. Other databases do not have the problem. And only > > with one particular server. The exact same database on a different server > > does not have the problem. > >Have you run VACUUM ANALYZE *as the superuser* on the faulty server >recently? > >From the look of the explain, PG is grossly underestimating the number of >items in the pg_trigger and pg_depend tables, and thus choosing an >inappropriate nested loop execution. > >-- >-Josh Berkus > Aglio Database Solutions > San Francisco --- Michael