pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: Michael Fuhr <mike@fuhr.org>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: vacuum full, why multiple times ?
Date: Wed, 09 Mar 2005 12:27:30 +0100
Message-ID: <422EDDA2.5000901@bigfoot.com> (raw)
In-Reply-To: <20050309021533.GB13883@winnie.fuhr.org>
References: <422E4B15.60806@bigfoot.com>
	<20050309021533.GB13883@winnie.fuhr.org>

Michael Fuhr wrote:
> On Wed, Mar 09, 2005 at 02:02:13AM +0100, Gaetano Mendola wrote:
> 
> 
>>Basically I'm noticing that a simple vacuum full is not enough to
>>shrink completelly the table:
>>
>># vacuum full verbose url;
>>INFO:  vacuuming "public.url"
>>INFO:  "url": found 268392 removable, 21286 nonremovable row versions in 8563 pages
>>DETAIL:  22 dead row versions cannot be removed yet.
> 
> 
> How busy is the database?  I'd guess that each time you run VACUUM,
> there are still open transactions that have visibility to the dead
> rows, so VACUUM doesn't touch them.  Those transactions eventually
> complete, and eventually VACUUM FULL does what you're expecting.
> I don't know if that's the only possible cause, but I get results
> similar to yours if I have transactions open when I run VACUUM.
> 

That was my first tough but it seem strange that 2 dead rows where
grabbing 7883 pages, don't you think ?


# 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




Regards
Gaetano Mendola







view thread (7+ messages)  latest in thread

Message-ID: <422EDDA2.5000901@bigfoot.com>
Permalink:  ../422EDDA2.5000901@bigfoot.com/
Also on:    postgresql.org/message-id/422EDDA2.5000901@bigfoot.com

 · 

reply

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: mendola@bigfoot.com, mike@fuhr.org
  Subject: Re: vacuum full, why multiple times ?
  In-Reply-To: <422EDDA2.5000901@bigfoot.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