Re: vacuum full, why multiple times ? - Mailing list pgsql-performance

From Gaetano Mendola
Subject Re: vacuum full, why multiple times ?
Date
Msg-id 422F086F.9080605@bigfoot.com
Whole thread Raw
In response to Re: vacuum full, why multiple times ?  (Richard Huxton <dev@archonet.com>)
Responses Re: vacuum full, why multiple times ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Huxton wrote:
> 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.

It's clear now.


Regards
Gaetano Mendola
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCLwhu7UpzwH2SGd4RAhEIAKDodnb03RvInDOJz9H+4w//DgJifACeNINP
0UMkQ0yBwNAZw91clvAUjRI=
=e+mM
-----END PGP SIGNATURE-----


pgsql-performance by date:

Previous
From: Richard Huxton
Date:
Subject: Re: vacuum full, why multiple times ?
Next
From: Tom Lane
Date:
Subject: Re: vacuum full, why multiple times ?