Re: question on TRUNCATE vs VACUUM FULL
| От | Chris |
|---|---|
| Тема | Re: question on TRUNCATE vs VACUUM FULL |
| Дата | |
| Msg-id | 47E0680D.6020101@gmail.com обсуждение исходный текст |
| Ответ на | question on TRUNCATE vs VACUUM FULL ("Mark Steben" <msteben@autorevenue.com>) |
| Ответы |
Re: question on TRUNCATE vs VACUUM FULL
|
| Список | pgsql-performance |
> > So my question is this: Shouldn’t VACUUM FULL clean Table C and reclaim > all its space? You've got concepts mixed up. TRUNCATE deletes all of the data from a particular table (and works in all dbms's). http://www.postgresql.org/docs/8.3/interactive/sql-truncate.html VACUUM FULL is a postgres-specific thing which does work behind the scenes to clean up MVCC left-overs. It does not touch any current data or records in the table, it's purely behind the scenes work. http://www.postgresql.org/docs/current/interactive/sql-vacuum.html The two have completely different uses and nothing to do with each other what-so-ever. -- Postgresql & php tutorials http://www.designmagick.com/
В списке pgsql-performance по дате отправления: