From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cutting down the TODO list thread |
Date: | 2021-12-09 00:11:57 |
Message-ID: | CAD21AoBdBs7AYPum20QvaNLPtETcvVzTQMUZG5y5CJO9TnBrfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Dec 9, 2021 at 2:40 AM John Naylor <john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> - Improve autovacuum tuning
> http://www.postgresql.org/message-id/5078AD6B.8060802@agliodbs.com
> http://www.postgresql.org/message-id/20130124215715.GE4528@alvh.no-ip.org
>
> I'm kind of on the fence about these. The title is way too broad, and
> I doubt we are going to forget to keep improving this area.
>
> It seems the first thread is really about auto-analyze thresholds, so
> maybe it should be in a separate entry if we want to do anything
> mentioned in the thread?
>
> The second thread is really about autovacuum launcher scheduling.
> Probably still relevant, but the thread is very long and doesn't seem
> terribly helpful to someone trying to get up to speed on the issues
> that are still relevant. I don't see any more recent discussion,
> either. Thoughts?
There is another discussion on autovacuum scheduling in 2018 here:
https://www.postgresql.org/message-id/0A3221C70F24FB45833433255569204D1F8A4DC6%40G01JPEXMBYT05
Some algorithms were proposed there and I implemented a PoC patch:
But not completed.
Regards,
--
Masahiko Sawada
EDB: https://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-12-09 00:12:10 | Re: Fix typos - "an" instead of "a" |
Previous Message | Masahiko Sawada | 2021-12-08 23:48:20 | Re: parallel vacuum comments |