Re: vacuumdb --freeze
От | Tom Lane |
---|---|
Тема | Re: vacuumdb --freeze |
Дата | |
Msg-id | 9858.1235064276@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: vacuumdb --freeze (Zeugswetter Andreas OSB sIT <Andreas.Zeugswetter@s-itsolutions.at>) |
Ответы |
Re: vacuumdb --freeze
|
Список | pgsql-hackers |
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...) 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. regards, tom lane
В списке pgsql-hackers по дате отправления: