I was having problems earlier with connecting to PostgreSQL via PgAdminIII, and google was no help. The problem was that connecting from the "psql" CLI remotely was fast, and the initial connect via PgAdminIII was fast, but opening a particular database hung PgAdminIII for several minutes.

For future reference, a postmaster process was taking up 100% CPU time on the server, and a "vacuum analyze pg_trigger" resolved the problem.

A tcpdump of the wire showed that there was this nasty query being sent referencing the pg_trigger table, which took 2 minutes to complete on a very fast CPU.
(Post Reply)