Request a Demo
Home   >   mailing lists

Re: Report oldest xmin source when autovacuum cannot remove tuples - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Report oldest xmin source when autovacuum cannot remove tuples
Date
Msg-id CAFiTN-te-2RBhz3AdcyQYVqyxkLKgK6xnvLaXgdo=Jc2ywFd9A@mail.gmail.com
Whole thread Raw
In response to Re: Report oldest xmin source when autovacuum cannot remove tuples  (Sami Imseih <samimseih@gmail.com>)
List pgsql-hackers
Tree view 
On Sat, Nov 15, 2025 at 5:56 AM Sami Imseih <samimseih@gmail.com> wrote:
>
> Thanks for starting this thread! This is a very useful
> feature that users will find beneficial to easily narrow
> down the reason the xmin horizon is being held back,
> and take action.

+1 for the idea.  In BackendXidFindCutOffReason() you have directly
reported using NOTICE I believe that is just to show the idea and you
are planning to append this to the main message?  Apart from that we
are looping the whole pgprocarray, however it is only done when we are
vacuuming with verbose mode so might not be that bad.

--
Regards,
Dilip Kumar
Google

pgsql-hackers by date:

Previous
From: wenhui qiu
Date:
Subject: Re: Report oldest xmin source when autovacuum cannot remove tuples
Next
From: Thomas Munro
Date:
Subject: Re: GNU/Hurd portability patches