From: | Armand du Plessis <adp(at)bank(dot)io> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
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-19 16:12:49 |
Message-ID: | CANf99sXOekH0m0TBE2uQJuUai0nRqiOE1mUwmoiyj8qTcL8EYQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sun, May 19, 2013 at 6:08 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 19 May 2013 13:54, Armand du Plessis <adp(at)bank(dot)io> wrote:
>
> > We started seeing 1000s of messages like the ones below in our logs
> starting
> > last night. There's been no changes but performance has dropped
> > significantly.
>
> > Any ideas what would be causing this?
>
> The database has not been issuing VACUUMs on some or all of the
> relations, so the system needs to issue "anti-transactional
> wraparound" VACUUMs.
>
Thanks, once I logged in with another user I saw there's one relation that
is being vacuumed to prevent tx wraparound. The sheer number of those log
entries made it seem like the autovacuum is in a loop.
>
> --
> Simon Riggs http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2013-05-20 00:36:48 | Re: Steps to switch from Master to standby mode : |
Previous Message | Simon Riggs | 2013-05-19 16:08:33 | Re: Transaction ID wrap limit is log entries |