Re: Oldest xmin is far in the past

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: Christian Rosnes <christian(dot)rosnes(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Oldest xmin is far in the past
Date: 2012-06-30 13:55:05
Message-ID: 87k3yogb0m.fsf@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Christian Rosnes <christian(dot)rosnes(at)gmail(dot)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(dot)consulting(at)comcast(dot)net
p: 732.216.7255

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Christian Rosnes 2012-06-30 14:22:14 Re: Oldest xmin is far in the past
Previous Message Christian Rosnes 2012-06-30 05:56:58 Oldest xmin is far in the past