Horton

Re: pg_upgrade and statistics

Kevin Grittner <kevin.grittner@wicourts.gov>

View thread
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-13T19:48:37Z
Lists: pgsql-hackers 
Bruce Momjian <bruce@momjian.us> wrote:
 
>>>> cir=# analyze "CaseHist";
>>>> ANALYZE
>>>> Time: 143450.467 ms
 
> 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".  :-(
 
We have a sister machine to the one used for that benchmark -- same
hardware and database.  The cost limit didn't seem to make much
difference:
 
cir=# set vacuum_cost_delay = 0;
SET
cir=# \timing on         
Timing is on.
cir=# analyze "CaseHist" ;
ANALYZE
Time: 146169.728 ms
 
So it really does seem to take that long.
 
-Kevin