From: Josh Berkus <josh@agliodbs.com>
To: Michael Shapiro <mshapiro@ncsa.edu>
To: pgsql-performance@postgresql.org
Subject: Re: PgAdmin startup query VERY slow
Date: Tue, 6 Jan 2004 13:01:43 -0800
Message-ID: <200401061301.43954.josh@agliodbs.com> (raw)
In-Reply-To: <5.2.0.9.2.20040106144745.00bcfe30@pop.ncsa.uiuc.edu>
References: <5.2.0.9.2.20040106144745.00bcfe30@pop.ncsa.uiuc.edu>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, mshapiro@ncsa.edu
Subject: Re: PgAdmin startup query VERY slow
In-Reply-To: <200401061301.43954.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox