From: Tom Lane <tgl@sss.pgh.pa.us>
To: Armand du Plessis <adp@bank.io>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Transaction ID wrap limit is log entries
In-reply-to: 
 <CANf99sXZ9m4J6QXxecFJprUF0Njs+WNn1RTWsiYHT9To_bnBSA@mail.gmail.com>
References: 
 <CANf99sUyKcOpuacR_Lms4JpAfOV1KnskJM4EFNSAB3x3-=zCRw@mail.gmail.com>
	<CA+U5nMKfm0xrMgy_ND=1LKBrYUCC0bU_g_=V7m_Jpa8zDe=scg@mail.gmail.com>
	<CANf99sXOekH0m0TBE2uQJuUai0nRqiOE1mUwmoiyj8qTcL8EYQ@mail.gmail.com>
	<CANf99sXZ9m4J6QXxecFJprUF0Njs+WNn1RTWsiYHT9To_bnBSA@mail.gmail.com>
Comments: In-reply-to Armand du Plessis <adp@bank.io>
	message dated "Mon, 20 May 2013 11:41:30 +0200"
Date: Mon, 20 May 2013 09:11:43 -0400
Message-ID: <3238.1369055503@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Armand du Plessis <adp@bank.io> writes:
> The autovacuum completed (after many hours) however it didn't seem to have
> frozen any old pages as it just kicks off again right away with the same
> reason (VACUUM ANALYZE public.messages (to prevent wraparound))

I suspect it's unable to move the table's min XID forward at all because
there is some old open transaction preventing cleanup of very old dead
tuples.  Look for old xact_start times in pg_stat_activity.  Also look
for old entries in pg_prepared_xacts.  If you find any, get rid of them.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin