Re: Too many autovacuum workers spawned during forced auto-vacuum

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Too many autovacuum workers spawned during forced auto-vacuum
Date: 2017-01-20 21:28:20
Message-ID: CA+TgmoZXYwoMJ+7Fn8Yj_ZR1ui8ODoBdYiZ78WeLGC6o8odWNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 20, 2017 at 2:43 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Fri, Jan 20, 2017 at 4:11 AM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
>> Robert Haas wrote:
>>
>>> After sleeping on this, I'm inclined to go with Amit's fix for now.
>>> It seems less likely to break anything in the back-branches than any
>>> other option I can think up.
>>
>> Yeah, no objections here.
>
> +1.

OK, committed and back-patched all the way.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-01-20 21:29:45 Re: Declarative partitioning - another take
Previous Message Alvaro Herrera 2017-01-20 21:25:18 Re: Vacuum: allow usage of more than 1GB of work mem