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 5ED51D1B49B for ; Tue, 6 Jan 2004 23:13:27 +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 92307-10 for ; Tue, 6 Jan 2004 19:12:39 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id A502DD1B47D for ; Tue, 6 Jan 2004 19:12:36 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i06NCZ19001688; Tue, 6 Jan 2004 18:12:35 -0500 (EST) To: josh@agliodbs.com Cc: Michael Shapiro , pgsql-performance@postgresql.org Subject: Re: PgAdmin startup query VERY slow In-reply-to: <200401061317.30877.josh@agliodbs.com> References: <5.2.0.9.2.20040106144745.00bcfe30@pop.ncsa.uiuc.edu> <5.2.0.9.2.20040106152859.02a17ea8@pop.ncsa.uiuc.edu> <200401061317.30877.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Tue, 06 Jan 2004 13:17:30 -0800" Date: Tue, 06 Jan 2004 18:12:35 -0500 Message-ID: <1687.1073430755@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/77 X-Sequence-Number: 5252 Josh Berkus writes: > Incidentally, just ANALYZE would probably have fixed your problem. ... or just VACUUM; that would have updated the row count which is all that was really needed here. The main point is that you do have to do that as superuser, since the same commands issued as a non-superuser won't touch the system tables (or any table you do not own). regards, tom lane