Re: pg_upgrade and statistics

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Bruce Momjian" <bruce@momjian.us>
Cc: "Daniel Farina" <daniel@heroku.com>,"Greg Stark" <stark@mit.edu>, "pgsql-hackers" <pgsql-hackers@postgresql.org>
Date: 2012-03-13T20:17:23Z
Lists: pgsql-hackers
Bruce Momjian <bruce@momjian.us> wrote:
 
> OK, so a single 44GB tables took 2.5 minutes to analyze;  that is
> not good.  It would require 11 such tables to reach 500GB (0.5
> TB), and would take 27 minutes.  The report I had was twice as
> long, but still in the ballpark of "too long".  :-(
 
But it's really 600 tables of different sizes, which wound up
actually taking:
 
cir=# analyze;
ANALYZE
Time: 3433794.609 ms
 
Just under one hour.
 
Now, if I remember right, the cluster was down for about three
minutes to run pg_upgrade.  Until there are some statistics for key
tables, though, it's not really usable.
 
-Kevin