Tom Lane wrote:
> Zeugswetter Andreas OSB sIT <Andreas.Zeugswetter@s-itsolutions.at> writes:
> > I am still answering here because my question was related to upgrade.
> > I think you need to turn off autovacuum before freezing to avoid a later analyze
> > that unfreezes pg_class (or the stats table).
>
> 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.
> The end goal is going to be to have all this work happen in a standalone
> backend, rather than risk firing up the postmaster while the database is
> in an unstable state. So I would counsel spending as little effort as
> possible on filing off rough edges that are related to the
> using-a-postmaster scenario.
Any idea how to do that? Would we have to leave the libpq API?
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +