Bruce Momjian <bruce(at)momjian(dot)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.
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2012-03-13 14:34:16|
|Subject: Re: pg_upgrade and statistics|
|Previous:||From: Tom Lane||Date: 2012-03-13 14:28:32|
|Subject: Re: Explicitly specifying use of IN/OUT variable in PL/pgSQL functions |