From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: vacuumdb --freeze |
Date: | 2009-02-17 23:52:25 |
Message-ID: | 200902172352.n1HNqPI11349@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2009-02-17 23:56:47 | regression test crashes at tsearch |
Previous Message | Tom Lane | 2009-02-17 23:49:38 | Re: vacuumdb --freeze |