Re: pg_upgrade and statistics - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: pg_upgrade and statistics
Date
Msg-id 4F5F58EE0200002500046246@gw.wicourts.gov
Whole thread Raw
In response to Re: pg_upgrade and statistics  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List 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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: LIST OWNED BY...
Next
From: Tom Lane
Date:
Subject: Re: Potential reference miscounts and segfaults in plpython.c