Re: Report oldest xmin source when autovacuum cannot remove tuples

From: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>
To: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
Cc: Scott Ray <scott(at)scottray(dot)io>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(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-10-02 07:48:32
Message-ID: CAOzEurQ8atKjCE95K-bPUWKHrBT03bT+VUj+MhxRF0iDj9SZkg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 2, 2026 at 3:20 PM wenhui qiu <qiuwenhuifx(at)gmail(dot)com> wrote:

> However, I would like to advocate strongly for keeping the distinction between
> active and idle-in-transaction sessions (which was present in earlier versions
> but dropped in v10).

Thanks for the review.

Reporting the active versus idle state is out of scope for this patch,
as Fujii-san suggested. I plan to address it in a follow-up patch.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2026-10-02 08:05:55 Re: PANIC serves too many masters
Previous Message Laurenz Albe 2026-10-02 07:30:21 Re: Adding a stored generated column without long-lived locks