Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <br...@momjian.us> writes:
> > > Tom Lane wrote:
> > >> vacuum analyze doesn't unfreeze pg_class. It could create unfrozen
> > >> tuples in pg_statistic, perhaps, but we could easily fix that by
> > >> truncating pg_statistic afterwards (its not like there will be useful
> > >> data there...)
> >
> > > I have added --analyze to the vacuumdb command and documented its
> > > purpose.
> >
> > Surely that's backwards? What's the point of doing analyze work you'll
> > have to throw away?
>
> Hmmm, that is true; removed.
I thought a little more and it seems best to make valid pg_statistics
entries rather than have entries who's xid status changes after moving
the new clog into place. Hopefully autovacuum will pick up on analyzing
the new database, and I will add a mention to the README:
Optimizer statistcs information is not transfered as part of the upgrade
so you should run 'vacuumdb --all --analyze'.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
