Re: vacuum full, why multiple times ?

From: Richard Huxton <dev(at)archonet(dot)com>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: vacuum full, why multiple times ?
Date: 2005-03-09 12:30:01
Message-ID: 422EEC49.7080202@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Gaetano Mendola wrote:
>
> # vacuum full verbose url;
> INFO: vacuuming "public.url"
> INFO: "url": found 74 removable, 21266 nonremovable row versions in 8550 pages
> DETAIL: 2 dead row versions cannot be removed yet.
> [SNIP]
> INFO: "url": moved 11 row versions, truncated 8550 to 8504 pages
>
>
> and in the next run:
>
>
> # vacuum full verbose url;
> INFO: vacuuming "public.url"
> INFO: "url": found 13 removable, 21264 nonremovable row versions in 8504 pages
> DETAIL: 0 dead row versions cannot be removed yet.
> [SNIP]
> INFO: "url": moved 5666 row versions, truncated 8504 to 621 pages

If page number 8549 was the one being held, I don't think vacuum can
truncate the file. The empty space can be re-used, but the rows can't be
moved to a lower page while a transaction is using them.

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Gaetano Mendola 2005-03-09 14:30:07 Re: vacuum full, why multiple times ?
Previous Message Hugo Ferreira 2005-03-09 12:08:21 Re: Help trying to tune query that executes 40x slower than in SqlServer