Re: Feedback on getting rid of VACUUM FULL
От | Robert Haas |
---|---|
Тема | Re: Feedback on getting rid of VACUUM FULL |
Дата | |
Msg-id | 603c8f070909170825m8499bd7w63d3ea8c409c8fe9@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Feedback on getting rid of VACUUM FULL (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Feedback on getting rid of VACUUM FULL
Re: Feedback on getting rid of VACUUM FULL |
Список | pgsql-hackers |
On Thu, Sep 17, 2009 at 10:21 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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. I'm a bit confused. CTIDs change all the time anyway, whenever you update the table. What could someone possibly be using them for? ...Robert
В списке pgsql-hackers по дате отправления: