From: Richard Huxton <dev@archonet.com>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: Michael Fuhr <mike@fuhr.org>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: vacuum full, why multiple times ?
Date: Wed, 09 Mar 2005 12:30:01 +0000
Message-ID: <422EEC49.7080202@archonet.com> (raw)
In-Reply-To: <422EDDA2.5000901@bigfoot.com>
References: <422E4B15.60806@bigfoot.com>
<20050309021533.GB13883@winnie.fuhr.org>
<422EDDA2.5000901@bigfoot.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dev@archonet.com, mendola@bigfoot.com, mike@fuhr.org
Subject: Re: vacuum full, why multiple times ?
In-Reply-To: <422EEC49.7080202@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox