Re: pg_upgrade and statistics - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: pg_upgrade and statistics
Date
Msg-id 4F5F135A02000025000461F5@gw.wicourts.gov
Whole thread Raw
In response to Re: pg_upgrade and statistics  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade and statistics  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> wrote:
> I just received a sobering blog comment stating that pg_upgrade
> took 5 minutes on a 0.5TB database, but analyze took over an hour:
Yeah, we have had similar experiences.  Even if this can't be done
for every release or for every data type, bringing over statistics
from the old release as a starting point would really help minimize
downtime on large databases.
Of course, release docs should indicate which statistics *won't* be
coming across, and should probably recommend a database ANALYZE or
VACUUM ANALYZE be done when possible.
-Kevin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Explicitly specifying use of IN/OUT variable in PL/pgSQL functions
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_upgrade and statistics