Robert Haas <robertmh...@gmail.com> wrote: > I noticed in Bruce's talk that there are a number of post-migration > steps which are currently partially manual. Ideally we'd like to > automate them all, preferably in some sort of well-thought-out order. > I actually suspect this is something like: analyze each database, > reindex those indices invalidated by the upgrade, analyze each > database again. We have found it useful to VACUUM FREEZE ANALYZE a converted database. The first access to any page will cause writing of hint bits, and we'd rather deal with that before we let the users in, to avoid having sluggish performance for them while that happens. The FREEZE part is to avoid a freeze of all subsequently untouched data in all tables at some unpredictable time -- potentially in the middle of a busy workday. The usual argument against aggressive freezing (that forensic information useful in recovery of a corrupted database) doesn't carry much weight right after a conversion. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
