Re: Transaction ID wrap limit is log entries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Armand du Plessis <adp(at)bank(dot)io>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Transaction ID wrap limit is log entries
Date: 2013-05-20 13:11:43
Message-ID: 3238.1369055503@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Armand du Plessis <adp(at)bank(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Armand du Plessis 2013-05-20 13:21:50 Re: Transaction ID wrap limit is log entries
Previous Message Armand du Plessis 2013-05-20 09:41:30 Re: Transaction ID wrap limit is log entries