pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Question on vacuum output
Date: Tue, 20 Jun 2006 17:08:28 -0400
Message-ID: <20060620210828.GH26882@surnet.cl> (raw)
In-Reply-To: <1d219a6f0606201349w48f2cfd0s68914352c76cb4a0@mail.gmail.com>
References: <1d219a6f0606201349w48f2cfd0s68914352c76cb4a0@mail.gmail.com>

Chris Hoover wrote:
> I am having some performance issues on some of my larger databases
> (50-100+GB).  I just ran a vacuum analyze on our key table, and saw this at
> the end.
> 
> DETAIL:  562499 dead row versions cannot be removed yet.

Is there an open, idle transaction on this database?  A leftover psql
session running in a forgotten, detached screen session maybe?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (2+ messages)

Message-ID: <20060620210828.GH26882@surnet.cl>
Permalink:  ../20060620210828.GH26882@surnet.cl/
Also on:    postgresql.org/message-id/20060620210828.GH26882@surnet.cl

 · 

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: alvherre@commandprompt.com, revoohc@gmail.com
  Subject: Re: Question on vacuum output
  In-Reply-To: <20060620210828.GH26882@surnet.cl>
  References: <1d219a6f0606201349w48f2cfd0s68914352c76cb4a0@mail.gmail.com> <20060620210828.GH26882@surnet.cl>

* 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