From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | john gale <john(at)smadness(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: how much disk space does a VACUUM FULL take? |
Date: | 2013-12-04 15:15:04 |
Message-ID: | CALd+dcck=wsKEF+GyZBPdHZ3M+jrEOisPfBUnyHhcY1wYXOHHg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 3, 2013 at 4:04 PM, john gale <john(at)smadness(dot)com> wrote:
> Does this suggest that VACUUM FULL needs free disk space on the order of
> the full size of the table that it's vacuuming to be able to complete? Or
> does it / can it write the filesystem files in the 1GB chunks stored in
> /base while removing the new "unused" files at the same time, thus
> requiring only a few GB of free space?
>
There are at least two tools out there that compact your table "live" by
arranging it such that the trailing pages of your table are empty (by
issuing trivial updates), and letting the standard vacuum truncate the file.
Start here:
http://www.depesz.com/2013/10/15/bloat-removal-without-table-swapping/
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-12-04 16:23:44 | Re: Postgres 9.3 read block error went into recovery mode |
Previous Message | Albe Laurenz | 2013-12-04 13:47:05 | Re: unexplainable psql exit status 1 |