Re: vacuumdb --freeze

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zeugswetter Andreas OSB sIT <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: vacuumdb --freeze
Date: 2009-02-19 18:24:52
Message-ID: 200902191824.n1JIOqR21882@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:
> > 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.

> >> The end goal is going to be to have all this work happen in a standalone
> >> backend,
>
> > Any idea how to do that?
>
> I didn't say it was easy.

Well, seeing as we want something for 8.4, I figured you had a plan.

--
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. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sam Mason 2009-02-19 18:29:25 Re: WIP: hooking parser
Previous Message Tom Lane 2009-02-19 18:20:49 Re: Fixing Grittner's planner issues