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

From Tom Lane
Subject Re: vacuumdb --freeze
Date
Msg-id 10312.1235065791@sss.pgh.pa.us
Whole thread Raw
In response to Re: vacuumdb --freeze  (Bruce Momjian <bruce@momjian.us>)
Responses Re: vacuumdb --freeze  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@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?

>> 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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: decibel
Date:
Subject: Knuth "nested parens" picture
Next
From: Tom Lane
Date:
Subject: Re: Fixing Grittner's planner issues