Re: Postgresql optimisation

On Wed, 28 Oct 2009, Dave Dutcher wrote:
> Also if you switch to truncate then you should ANALYSE the tables after you
> finish inserting. Note that VACUUM ANALYSE is not necessary after a
> truncate/insert because there should be no dead tuples to vacuum.

Perhaps reading the other replies in the thread before replying yourself
might be advisable, because this previous reply directly contradicts you:

On Wed, 28 Oct 2009, Kevin Grittner wrote:
> I recommend VACUUM ANALYZE of the table(s) after this step. Without
> that, the first query to read each tuple sets its hint bits and
> rewrites it, causing a surprising delay at unpredictable times
> (although heavier near the start of the day).

There *is* a benefit of running VACUUM ANALYSE rather than just ANALYSE.

Matthew

--
I suppose some of you have done a Continuous Maths course. Yes? Continuous
Maths? <menacing stares from audience> Whoah, it was like that, was it!
-- Computer Science Lecturer