Re: vacuumdb question/problem

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "David Ondrejik" <David(dot)Ondrejik(at)noaa(dot)gov>, "pgsql-admin" <pgsql-admin(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: vacuumdb question/problem
Date: 2011-07-15 19:17:47
Message-ID: 4E204C0B020000250003F3AB@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

David Ondrejik <David(dot)Ondrejik(at)noaa(dot)gov> wrote:

> So I had to kill my process, recover disk space and get the
> machine back in working condition for the weekend. I guess I will
> attempt to do the full vacuum again next week.

Why do you think that you need a VACUUM FULL? That is only needed
as an extreme measure in rather unusual circumstances. We run
hundreds of PostgreSQL databases, and have not used VACUUM FULL for
years. On the other hand, we VACUUM ANALYZE most databases in their
entirety every night. (Be very careful not to confuse VACUUM FULL
with vacuum of an entire database.)

On the other hand, the failed attempt at VACUUM FULL may have
bloated your indexes, so you might want to REINDEX the table next
week, followed by a VACUUM ANALYZE (without the FULL).

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Isabella Ghiurea 2011-07-15 19:40:00 PG 8.4 and identity columns
Previous Message Tom Lane 2011-07-15 19:11:11 Re: vacuumdb question/problem