Re: Vacuuming

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Paul Lambert <paul(dot)lambert(at)autoledgers(dot)com(dot)au>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Vacuuming
Date: 2007-05-08 04:20:19
Message-ID: 22584.1178598019@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I wrote:
>> Is there any point in vacuuming?

> The only thing a vacuum would do for you there is set the commit hint
> bits on the newly-inserted rows. Which might be worth doing if you want
> to get the table into a totally "clean" state, but it's probably a bit
> excessive. SELECTs on the table will set the hint bits anyway as
> they visit not-yet-hinted rows, so it's really a matter of do you want
> to pay that overhead all at once or spread-out.

I forgot to mention that any other operation that examines every table
row will fix all the hint bits as well. In particular a CREATE INDEX
would do that --- so if you are planning to create some indexes then
there's certainly no point in a VACUUM just after a table load.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2007-05-08 04:40:22 Re: tokenize string for tsearch?
Previous Message Tom Lane 2007-05-08 04:17:28 Re: Vacuuming