update, truncate and vacuum

Поиск
Список
Период
Сортировка
От Scott Feldstein
Тема update, truncate and vacuum
Дата
Msg-id B195EEA2-7B5D-444F-8F48-46BB88FCFFA8@hyperic.com
обсуждение исходный текст
Ответы Re: update, truncate and vacuum  ("Dave Dutcher" <dave@tridecap.com>)
Список pgsql-performance
Hi,
I have a couple questions about how update, truncate and vacuum would
work together.

1) If I update a table foo (id int, value numeric (20, 6))
with
update foo set value = 100 where id = 1

Would a vacuum be necessary after this type of operation since the
updated value is a numeric? (as opposed to a sql type where its size
could potentially change i.e varchar)

2) After several updates/deletes to a table, if I truncate it, would
it be necessary to run vacuum in order to reclaim the space?

thanks,
Scott

В списке pgsql-performance по дате отправления:

Предыдущее
От: "Jignesh K. Shah"
Дата:
Сообщение: Re: User concurrency thresholding: where do I look?
Следующее
От: "Luke Lonergan"
Дата:
Сообщение: Re: update, truncate and vacuum