analyze after a database restore?

From: mlw <pgsql(at)mohawksoft(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: analyze after a database restore?
Date: 2003-02-27 17:27:44
Message-ID: 3E5E4A90.1020605@mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just dumped and restored a rather large database, I upgraded from
7.2.x to 7.3.x. When I went to test my application against the new
database, it was dog slow. It had all the indexes, and looked fine.

Then it dawned on me, Doh! ANALYZE!

Should pg_dump appened an ANALYZE for each table?

On small tables, this shouldn't take too long. On large tables, you're
gonna have to do it anyway. I guess it could be an option as well.

It just seems like on of the tasks that is required for a "restored"
database to work properly, and as such, should probably be specified in
the backup procedure.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-02-27 17:37:54 Re: Can pessimistic locking be emulated?
Previous Message Tom Lane 2003-02-27 17:24:50 Re: Free-space-map management thoughts