| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dmitry O Litvintsev <litvinse(at)fnal(dot)gov> |
| Cc: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: autovacuum holds exclusive lock on table preventing it from to be updated |
| Date: | 2017-06-19 17:42:32 |
| Message-ID: | 20170619174232.7ltssvo6axg2iejb@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dmitry O Litvintsev wrote:
> Hi
>
> Since I have posted this nothing really changed. I am starting to panic (mildly).
...
> vacuum_cost_delay = 50ms
Most likely, this value is far too high. You're causing autovacuum to
sleep for a very long time with this setting. Hard to say for certain
without seeing the cost_limit value and the other related parameters,
but it's most certainly what's causing you pain. The default of 20ms is
already too high for most users.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2017-06-19 18:16:36 | Re: autovacuum holds exclusive lock on table preventing it from to be updated |
| Previous Message | Dmitry O Litvintsev | 2017-06-19 17:33:23 | Re: autovacuum holds exclusive lock on table preventing it from to be updated |