pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Subbiah, Stalin <SSubbiah@netopia.com>
To: pgsql-admin@postgresql.org
Subject: Vacuum Verbose output
Date: Mon, 31 Oct 2005 12:13:27 -0800
Message-ID: <6B26A56846293C4488B54CF3E440335403E2F77A@mxca2.corp.netopia.com> (raw)

Hi All,

We vacuum busy tables in different frequencies depending on how busy the
table is. Today I noticed that one of the task that was suppose to
delete rows from a busy table was running for a long time. And below is
the output of vacuum verbose after the task was stopped from running.
Trying to understand if the table/index has been bloated or not.

INFO:  vacuuming "public.eventlog"
INFO:  index "ix_eventlog_eventtime" now contains 11465395 row versions
in 77113 pages
DETAIL:  8737797 index row versions were removed.

Does it mean ix_eventlog_ index had 11.4mil row versions out of which
8.7mil were removed cause of deletes?

33189 index pages have been deleted, 0 are currently reusable.

Does it mean out of 77113 index pages, 33189 were deleted?

CPU 5.24s/13.76u sec elapsed 67.05 sec.


INFO:  "eventlog": removed 8737797 row versions in 361856 pages
DETAIL:  CPU 14.53s/22.00u sec elapsed 122.13 sec.
INFO:  index "ix_eventlog_eventtime" now contains 8023399 row versions
in 77116 pages
DETAIL:  3442698 index row versions were removed.
46439 index pages have been deleted, 0 are currently reusable.
CPU 3.18s/5.35u sec elapsed 22.85 sec.
INFO:  "eventlog": removed 3442698 row versions in 143144 pages
DETAIL:  CPU 5.64s/8.74u sec elapsed 69.15 sec.
INFO:  "eventlog": found 12180495 removable, 8022620 nonremovable row
versions in 837938 pages
DETAIL:  0 dead row versions cannot be removed yet.

There were 154716 unused item pointers.
0 pages are entirely empty.
CPU 44.37s/54.07u sec elapsed 357.04 sec.

Why does index and table INFO reported twice with different row version
numbers on a vacuum run.

Thanks,
Subbiah
Postgres v7.4.7

view thread (6+ messages)  latest in thread

Message-ID: <6B26A56846293C4488B54CF3E440335403E2F77A@mxca2.corp.netopia.com>
Permalink:  ../6B26A56846293C4488B54CF3E440335403E2F77A@mxca2.corp.netopia.com/
Also on:    postgresql.org/message-id/6B26A56846293C4488B54CF3E440335403E2F77A@mxca2.corp.netopia.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: SSubbiah@netopia.com
  Subject: Re: Vacuum Verbose output
  In-Reply-To: <6B26A56846293C4488B54CF3E440335403E2F77A@mxca2.corp.netopia.com>
  References: <6B26A56846293C4488B54CF3E440335403E2F77A@mxca2.corp.netopia.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