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:

> 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


---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Reply via email to