Re: Report oldest xmin source when autovacuum cannot remove tuples

From: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: wenhui qiu <qiuwenhuifx(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-07-07 16:34:06
Message-ID: CAOzEurTXvafJP6X3vpDt9eHEt0FKYWiWJQ0H_dWnt23XLWA9Kg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rebased the patches, as v8 no longer applied cleanly on the latest
master. The rebased v9 patches are attached.

Also, in my earlier reply to Bharath I referred to [1] but forgot to
include the reference itself, so I am adding it here.

[1] https://www.postgresql.org/message-id/CAA5RZ0sjMgMo4Xg-niyyF-CpkQ_CK6uOfNKYT%3D9RmiBkAxQkbQ%40mail.gmail.com

--
Best regards,
Shinya Kato
NTT OSS Center

Attachment Content-Type Size
v9-0001-Add-infrastructure-to-identify-what-holds-back-th.patch application/octet-stream 24.6 KB
v9-0002-Report-oldest-xmin-blocker-when-VACUUM-cannot-rem.patch application/octet-stream 19.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2026-07-07 16:50:27 Re: Mark class_descr strings for translation
Previous Message Shinya Kato 2026-07-07 16:16:21 Re: Report oldest xmin source when autovacuum cannot remove tuples