pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris White (cjwhite) <cjwhite@cisco.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Help understanding VACUUM info on 7.4.5
Date: Fri, 1 Apr 2005 13:23:52 -0800
Message-ID: <200504012123.j31LNpgS000922@sj-core-3.cisco.com> (raw)
In-Reply-To: <28606.1112389598@sss.pgh.pa.us>

Does this mean it could be any transaction, even one that has not done
anything with large objects, but one that started prior to the large objects
being deleted?

All access to the DB is done via JDBC, so has this JDBC issue been fixed in
7.4.5?

Chris

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Friday, April 01, 2005 1:07 PM
To: cjwhite@cisco.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Help understanding VACUUM info on 7.4.5 

"Chris White (cjwhite)" <cjwhite@cisco.com> writes:
> Below I have info which shows a DB which has had all objects deleted 
> and then vacuumed. As can been seen it say it has "9014 dead rows that 
> can't been removed". What does that mean?

That means there's an open transaction that is old enough to be able to see
those rows under MVCC rules, so VACUUM dare not remove them.

Check for clients that are issuing a BEGIN and then sitting with the
transaction open.  Older versions of JDBC did that behind your back, IIRC.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster



view thread (5+ messages)  latest in thread

Message-ID: <200504012123.j31LNpgS000922@sj-core-3.cisco.com>
Permalink:  ../200504012123.j31LNpgS000922@sj-core-3.cisco.com/
Also on:    postgresql.org/message-id/200504012123.j31LNpgS000922@sj-core-3.cisco.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: cjwhite@cisco.com, tgl@sss.pgh.pa.us
  Subject: Re: Help understanding VACUUM info on 7.4.5
  In-Reply-To: <200504012123.j31LNpgS000922@sj-core-3.cisco.com>
  References: <28606.1112389598@sss.pgh.pa.us> <200504012123.j31LNpgS000922@sj-core-3.cisco.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