Re: Report oldest xmin source when autovacuum cannot remove tuples

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Scott Ray <scott(at)scottray(dot)io>
Cc: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, laurenz(dot)albe(at)cybertec(dot)at, japinli(at)hotmail(dot)com, qiuwenhuifx(at)gmail(dot)com, samimseih(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Report oldest xmin source when autovacuum cannot remove tuples
Date: 2026-07-13 15:06:30
Message-ID: CAOYmi+k_cfkv=2eOs4b5t2R9q_wnVPiMyhLr1MbWW6taT_K_cg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 11, 2026 at 5:52 PM Scott Ray <scott(at)scottray(dot)io> wrote:
> I thought that posting the full patch here might confuse cfbot, so I
> decided to create a new thread and CF entry.

(I think the current convention is to name the patch file(s) with a
`nocfbot-` prefix, and then it'll be ignored.)

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2026-07-13 15:40:07 Re: Missing FSM Update when Updating VM On-access
Previous Message Karina Litskevich 2026-07-13 15:00:47 Implicit conversion from int64 to int32 when calling hash_get_num_entries