need vacuum after insert/truncate/insert? - Mailing list pgsql-performance

From Craig A. James
Subject need vacuum after insert/truncate/insert?
Date
Msg-id 44ADBDB8.5010008@modgraph-usa.com
Whole thread Raw
In response to Query plan issue when upgrading to postgres 8.14 (from postgres 8.12 or 7.4)  (Ioana Danes <ioanasoftware@yahoo.ca>)
Responses Re: need vacuum after insert/truncate/insert?  (Markus Schaber <schabi@logix-tt.com>)
List pgsql-performance
If I insert a bunch of rows, then truncate, then insert a bunch more rows, do I need to vacuum?  I've been assuming
thatTRUNCATE TABLE is a brute-force technique that more-or-less tosses the old table and starts fresh so that no vacuum
isnecessary. 

Second question: Same scenario as above, but now the table has indexes.  Is a reindex needed, or are the indexes they
"truncated"too? 

Thanks,
Craig


pgsql-performance by date:

Previous
From: Chris
Date:
Subject: Re: Query plan issue when upgrading to postgres 8.14 (from
Next
From: Michael Loftis
Date:
Subject: Re: suggested RAID controller for FreeBSD 6.1 +PostgreSQL