From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tim Bellis <Tim(dot)Bellis(at)metaswitch(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Subject: | Re: Autovacuum stuck for hours, blocking queries |
Date: | 2017-02-16 22:49:32 |
Message-ID: | 20170216224932.fsufp4fssamurq2x@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Also you might want to look into how you got into a situation where
> you have an anti-wraparound vacuum that's taking so long to run.
If there are ALTERs running all the time, regular (non-anti-wraparound)
vacuums would be canceled and never get a chance to run. Eventually,
autovacuum decides it's had enough and doesn't cancel anymore, so
everyone else gets stuck behind.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Hinkle | 2017-02-16 23:27:50 | Re: Bad planning data resulting in OOM killing of postgres |
Previous Message | Tom Lane | 2017-02-16 22:39:31 | Re: Autovacuum stuck for hours, blocking queries |