From: Chris <dmagick@gmail.com>
To: Mark Steben <msteben@autorevenue.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: question on TRUNCATE vs VACUUM FULL
Date: Wed, 19 Mar 2008 12:10:37 +1100
Message-ID: <47E0680D.6020101@gmail.com> (raw)
In-Reply-To: <00f701c8893b$f9545af0$14010a0a@dei26g028575>
References: <00f701c8893b$f9545af0$14010a0a@dei26g028575>
>
> 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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dmagick@gmail.com, msteben@autorevenue.com
Subject: Re: question on TRUNCATE vs VACUUM FULL
In-Reply-To: <47E0680D.6020101@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox