Re: Transaction ID wrap limit is log entries
| От | Armand du Plessis |
|---|---|
| Тема | Re: Transaction ID wrap limit is log entries |
| Дата | |
| Msg-id | CANf99sXOekH0m0TBE2uQJuUai0nRqiOE1mUwmoiyj8qTcL8EYQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Transaction ID wrap limit is log entries (Simon Riggs <simon@2ndQuadrant.com>) |
| Ответы |
Re: Transaction ID wrap limit is log entries
|
| Список | pgsql-admin |
On Sun, May 19, 2013 at 6:08 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
On 19 May 2013 13:54, Armand du Plessis <adp@bank.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
В списке pgsql-admin по дате отправления: