pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Copley <kcopley@bart.gov>
To: pgsql-admin@postgresql.org
Subject: vacuumdb -v output
Date: Thu, 21 Apr 2005 10:59:54 -0700
Message-ID: <003301c5469b$eead09c0$0b02a594@csekcopley2> (raw)

Hi,
I've just put a system into production in which some tables are updated frequently - several times per second.
I'm doing a nightly vacuumdb -v, but am not sure if it's achieving anything. Here's the output for one table:

----------------------------------------------------------------------------------------------------------------------------------------------------
INFO:  vacuuming "public.fip_track_circuit"
INFO:  index "fip_track_circuit_pk" now contains 1557427 row versions in 4538 pages
DETAIL:  10 index row versions were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.22s/0.14u sec elapsed 6.51 sec.
INFO:  "fip_track_circuit": removed 10 row versions in 9 pages
DETAIL:  CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  "fip_track_circuit": found 10 removable, 1557427 nonremovable row versions in 14305 pages
DETAIL:  1555321 dead row versions cannot be removed yet.
There were 1 unused item pointers.
0 pages are entirely empty.
CPU 0.42s/0.24u sec elapsed 6.82 sec.
INFO:  vacuuming "public.fip_xl_switch"
----------------------------------------------------------------------------------------------------------------------------------------------------

I'm concerned about ".... 1555321 dead row versions cannot be removed yet...."

I'd be extremely grateful if anyone could cast some light on this.
Thanks, Kevin



view thread (2+ messages)  latest in thread

Message-ID: <003301c5469b$eead09c0$0b02a594@csekcopley2>
Permalink:  ../003301c5469b$eead09c0$0b02a594@csekcopley2/
Also on:    postgresql.org/message-id/003301c5469b$eead09c0$0b02a594@csekcopley2

 · 

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: kcopley@bart.gov
  Subject: Re: vacuumdb -v output
  In-Reply-To: <003301c5469b$eead09c0$0b02a594@csekcopley2>
  References: <003301c5469b$eead09c0$0b02a594@csekcopley2>

* 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