On Tue, Dec 3, 2013 at 3:30 PM, Greg Stark <stark@mit.edu> wrote:
At multiple conferences I've heard about people trying all sorts of gymnastics to avoid ANALYZE which they expect to take too long and consume too much I/O. This is especially a big complain after upgrades when their new database performs poorly until the new statistics are in and they did pg_upgrade to avoid an extended downtime and complain about ANALYZE taking hours.
Out of curiosity, are they using the 3 stage script "analyze_new_cluster.sh"? If so, is the complaint that even the first rounds are too slow, or that the database remains unusable until the last round is complete?
