Re: Make autovacuum sort tables in descending order of xid_age

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Dilger <hornschnorter(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, Christophe Pettus <xof(at)thebuild(dot)com>
Subject: Re: Make autovacuum sort tables in descending order of xid_age
Date: 2020-08-03 06:53:15
Message-ID: 20200803065315.GN3317@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 30, 2020 at 09:20:15AM -0700, Mark Dilger wrote:
> I have not been working on this issue lately, but as I recall, my
> concern was that changing the behavior of autovacuum could introduce
> regressions for some users, so we should be careful to get it right
> before we rush to release anything. It didn't seem like the
> proposed changes took enough into account. But that's clearly a
> judgement call, having to do with how cautious any particular person
> thinks we should be. I don't feel strongly enough to stand in the
> way if the general concensus is that this is a good enough
> implementation.

Echoing with what has been already mentioned on this thread, I think
that autovacuum scheduling is a hard problem, and I would be rather
scared to change by default a behavior that has proved to work in some
cases, but could potentially doom others. I have an idea though: we
could make the scheduling behavior of autovacuum optional.

Anyway, the thread has stalled for a couple of months now, and we
don't have a clear consensus about this approach, so I am marking this
thread as returned with feedback.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-08-03 06:59:37 Replace remaining StrNCpy() by strlcpy()
Previous Message Michael Paquier 2020-08-03 06:47:13 Re: Add MAIN_RELATION_CLEANUP and SECONDARY_RELATION_CLEANUP options to VACUUM