Re: question on TRUNCATE vs VACUUM FULL - Mailing list pgsql-performance

From Chris
Subject Re: question on TRUNCATE vs VACUUM FULL
Date
Msg-id 47E0680D.6020101@gmail.com
Whole thread Raw
In response to question on TRUNCATE vs VACUUM FULL  ("Mark Steben" <msteben@autorevenue.com>)
Responses Re: question on TRUNCATE vs VACUUM FULL
List 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 by date:

Previous
From: Craig Ringer
Date:
Subject: Re: What is the best way to storage music files in Postgresql
Next
From: Craig Ringer
Date:
Subject: Re: What is the best way to storage music files in Postgresql