From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Michael Shapiro <mshapiro@ncsa.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: PgAdmin startup query VERY slow
Date: Tue, 06 Jan 2004 18:12:35 -0500
Message-ID: <1687.1073430755@sss.pgh.pa.us> (raw)
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>
Josh Berkus <josh@agliodbs.com> 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
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: tgl@sss.pgh.pa.us, josh@agliodbs.com, mshapiro@ncsa.edu
Subject: Re: PgAdmin startup query VERY slow
In-Reply-To: <1687.1073430755@sss.pgh.pa.us>
* 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