| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How about a option to disable autovacuum cancellation on lock conflict? |
| Date: | 2014-12-02 19:02:07 |
| Message-ID: | 547E0CAF.3060306@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/02/2014 10:35 AM, Alvaro Herrera wrote:
> If the table is large, the time window for this to happen is large also;
> there might never be a time window large enough between two lock
> acquisitions for one autovacuum run to complete in a table. This
> starves the table from vacuuming completely, until things are bad enough
> that an emergency vacuum is forced. By then, the bloat is disastrous.
>
> I think it's that suicide that Andres wants to disable.
A much better solution for this ... and one which would solve a *lot* of
other issues with vacuum and autovacuum ... would be to give vacuum a
way to track which blocks an incomplete vacuum had already visited.
This would be even more valuable for freeze.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-12-02 19:08:59 | Re: How about a option to disable autovacuum cancellation on lock conflict? |
| Previous Message | Josh Berkus | 2014-12-02 18:59:49 | Re: Turning recovery.conf into GUCs |