Re: Feedback on getting rid of VACUUM FULL
От | Tom Lane |
---|---|
Тема | Re: Feedback on getting rid of VACUUM FULL |
Дата | |
Msg-id | 10262.1253197314@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Feedback on getting rid of VACUUM FULL (Hannu Krosing <hannu@2ndQuadrant.com>) |
Ответы |
Re: Feedback on getting rid of VACUUM FULL
Re: Feedback on getting rid of VACUUM FULL Re: Feedback on getting rid of VACUUM FULL |
Список | pgsql-hackers |
Hannu Krosing <hannu@2ndQuadrant.com> writes: > On Wed, 2009-09-16 at 21:19 -0400, Tom Lane wrote: >> VACUUM FULL CONCURRENTLY is a contradiction in terms. Wishing it were >> possible doesn't make it so. > It depends on what do you mean by "VACUUM FULL" Anything that moves tuples is not acceptable as a hidden background operation, because it will break applications that depend on CTID. The utility Heikki is talking about is something that DBAs would invoke explicitly, presumably with an understanding of the side effects. regards, tom lane
В списке pgsql-hackers по дате отправления: