| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Craig James <cjames(at)emolecules(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: auto-vacuum vs. full table update |
| Date: | 2012-04-26 19:53:32 |
| Message-ID: | 4F99A7BC.3030709@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 04/26/2012 12:49 PM, Craig James wrote:
>
> An update to our system means I'm going to be rewriting every row of
> some large tables (20 million rows by 15 columns). In a situation
> like this, can auto-vacuum take care of it, or should I plan on
> vacuum-full/reindex to clean up?
>
If you rewrite the whole table, you will end up with a table twice the
size, it will not be compacted but as the table grows, the old space
will be reused.
jD
> This is 8.4.4.
>
> Thanks,
> Craig
>
--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2012-04-26 20:00:19 | Re: auto-vacuum vs. full table update |
| Previous Message | Craig James | 2012-04-26 19:49:31 | auto-vacuum vs. full table update |