Re: Report oldest xmin source when autovacuum cannot remove tuples

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>
Cc: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Report oldest xmin source when autovacuum cannot remove tuples
Date: 2026-05-23 13:35:37
Message-ID: 6634e1b0b5b74e5c2e3b06201120a81e11d82a55.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 2026-05-23 at 15:00 +0900, Shinya Kato wrote:
> Oops, I made a slight mistake. Fixed.

I think that is a great feature that will improve users' lives!

The patch looks fine to me too.
I guess the overhead of one more scan of the process array for every autovacuum
run if "log_autovacuum_min_duration" is non-zero (which is the default)
is acceptable.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-05-23 15:29:35 Re: Adding REPACK [concurrently]
Previous Message Daniil Davydov 2026-05-23 13:29:09 ERROR during COMMIT PREPARED can leave orphaned locks