Re: Report oldest xmin source when autovacuum cannot remove tuples

From: Scott Ray <scott(at)scottray(dot)io>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
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-17 18:11:54
Message-ID: Aw_2yS-BjfovFpGPT7K6Q8lK7h6jh8yas_IpuJN0vs-G7OegxJbeLs0R7XfOJnTKnFEFuAZlv6J8ov-mN1e3ysC2_K4nMUQlDdMFKe_vZ1Y=@scottray.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday, July 13th, 2026 at 8:06 AM, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:

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

Thanks for the tip.

--
Scott Ray

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-07-17 19:02:55 Re: walsummarizer can get stuck when switching timelines
Previous Message Masahiko Sawada 2026-07-17 17:56:15 Re: Follow-up fixes for online wal_level change