Re: vacuumdb --freeze - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: vacuumdb --freeze
Date
Msg-id 200902172352.n1HNqPI11349@momjian.us
Whole thread Raw
In response to Re: vacuumdb --freeze  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: vacuumdb --freeze  (Zeugswetter Andreas OSB sIT <Andreas.Zeugswetter@s-itsolutions.at>)
Re: vacuumdb --freeze  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I would like to add a --freeze parameter to vacuumdb for use by the
> > binary upgrade utility, and for symmetry with the existing VACUUM
> > options;  patch attached.
> 
> Exactly what do you think the upgrade utility is going to do with it?
> Surely not a database-wide VACUUM FREEZE, if we are hoping that upgrade
> is going to be fast.
> 
> As far as I can see this is a solution looking for a problem.

I didn't go into the use-case.  The way pg_migrator works is to copy the
_schema_ from the old database and load it into the new database.  We
then need to run vacuum freeze on the schema-only databases because we
then move pg_clog from the old database to the new one; so, it is
needed, and it will not take long to run.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: vacuumdb --freeze
Next
From: Hiroshi Inoue
Date:
Subject: regression test crashes at tsearch