-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Sent: Tuesday, March 18, 2008 9:11 PM
To: Mark Steben
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] question on TRUNCATE vs VACUUM FULL
So my question is this: Shouldn't VACUUM FULL clean Table C
Mark Steben escribió:
My confusion lies in the fact that we empty table C after
Function D finishes. There aren't any current data or records
To touch on the table. The MVCC leftovers are all purely dead
Rows that should be deleted.
Not if there are open transactions that might want to look
-
From: Bill Moran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 9:35 AM
To: Mark Steben
Cc: 'Chris'; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] question on TRUNCATE vs VACUUM FULL
In response to Mark Steben [EMAIL PROTECTED]:
I know what Vacuum full and truncate
In response to Mark Steben [EMAIL PROTECTED]:
Bill,
Thanks for your quick response.
We are at version 8.2.5 - just recently upgraded from 7.4.5.
This strategy using truncate was just implemented yesterday.
Now I will revisit the vacuum full strategy. Does seem to
Be redundant.
Is there a
Hi folks,
We are running Postgres 8.2.5.
I have 3 tables, call them A, B, and C
Table A houses info on all emails that have ever been created for the
purpose of being delivered to our end customers.
Big table. About 23 million rows.
Table B, the 'holding' table is populated with Table A
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
