Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 9AA9EE292B1
	for <pgsql-admin@postgresql.org>; Sat, 30 Jun 2012 10:55:23 -0300 (ADT)
Received: from qmta08.westchester.pa.mail.comcast.net ([76.96.62.80])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <gsievers19@comcast.net>) id 1Sky8u-0000C2-Oz
	for pgsql-admin@postgresql.org; Sat, 30 Jun 2012 13:55:22 +0000
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72])
	by qmta08.westchester.pa.mail.comcast.net with comcast
	id Udp31j0051ZXKqc58dv6Wq; Sat, 30 Jun 2012 13:55:06 +0000
Received: from homie ([68.45.149.190])
	by omta21.westchester.pa.mail.comcast.net with comcast
	id UdvE1j00946izrY3hdvExe; Sat, 30 Jun 2012 13:55:14 +0000
Received: by homie (Postfix, from userid 1000)
	id 7D396181CD7; Sat, 30 Jun 2012 09:55:05 -0400 (EDT)
To: Christian Rosnes <christian.rosnes@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Oldest xmin is far in the past
References: 
 <CAMgLkJMtdX01PLSr5FjbR-3Cgr1XvR3XXGPzTojjBV67LuxRMg@mail.gmail.com>
From: Jerry Sievers <gsievers19@comcast.net>
Date: Sat, 30 Jun 2012 09:55:05 -0400
In-Reply-To: 
 <CAMgLkJMtdX01PLSr5FjbR-3Cgr1XvR3XXGPzTojjBV67LuxRMg@mail.gmail.com>
	(Christian Rosnes's message of "Sat\,
	30 Jun 2012 07\:56\:58 +0200")
Message-ID: <87k3yogb0m.fsf@comcast.net>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Pg-Spam-Score: -0.7 (/)
X-Archive-Number: 201206/124
X-Sequence-Number: 39715

Christian Rosnes <christian.rosnes@gmail.com> writes:

> Hi,
>
> Coming back from vacation, I find a PostgreSQL database cluster (Pg version: 9.0.4)
> with 5 databases, which for the past 5 days have logged these messages:
>
> ? WARNING:? oldest xmin is far in the past
> ? HINT:? Close open transactions soon to avoid wraparound problems.
>
> The cluster has been running continously for over 9 months with autovacuum enabled.

<snip>>

> I cannot find any 'idle in transaction' connected, and I can see one 'idle' connection
> (but not 'idle in transaction') which is almost 24 hours old, the rest is from early this morning.
>
See if there is a prepared transaction still open.  Query pg_prepared_xacts.

HTH

-- 
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 732.216.7255