Re: Changing the autovacuum launcher scheduling; oldest table first algorithm

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>
Subject: Re: Changing the autovacuum launcher scheduling; oldest table first algorithm
Date: 2018-10-02 02:42:20
Message-ID: 20181002024220.GJ11712@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 28, 2018 at 04:20:53PM +0900, Masahiko Sawada wrote:
> If there is an up-to-date information meaning either that there is no
> tables needing vacuum or that there is only table needing vacuum but
> being vacuumed by other worker, AV launcher can launches new one to
> other database.

I am not completely sure what we want to do with this patch in
particular as there are many approaches and things which can be
discussed. For now, the latest patch proposed does not apply, so I am
moving it to next CF, waiting for its author.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-10-02 02:49:05 Re: WIP: BRIN multi-range indexes
Previous Message Michael Paquier 2018-10-02 02:33:17 Re: jsonpath