Re: pg_upgrade and statistics
Kevin Grittner <kevin.grittner@wicourts.gov>
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Bruce Momjian" <bruce@momjian.us>, "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: "Daniel Farina" <daniel@heroku.com>,"Greg Stark" <stark@mit.edu>, "pgsql-hackers" <pgsql-hackers@postgresql.org>
Date: 2012-03-13T19:25:50Z
Lists: pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote: > Bruce Momjian <bruce@momjian.us> wrote: >> That is 2.5 minutes. How large is that database? I dug around a little and found that we had turned on vacuum cost limits on the central databases, because otherwise the web team complained about performance during maintenance windows. On the county database we generally don't have users working all night, so we do maintenance during off hours, and run without cost-based limits. When the full run completes, I'll try analyze on that table again, in a session with the limits off. Maybe vacuumdb should have an option to disable the limits, and we recommend that after pg_upgrade? -Kevin