| From: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> |
|---|---|
| To: | Scott Ray <scott(at)scottray(dot)io> |
| Cc: | 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-06-03 01:24:29 |
| Message-ID: | CAOzEurTohto7mfbmGu0GCHgAF+6roKxZgartyYydWsDkg3HzTg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 3, 2026 at 10:05 AM Scott Ray <scott(at)scottray(dot)io> wrote:
> I've been working on a view like this. It shows the horizon
> contribution for each backend, prepared xact, replication slot, and
> HSF walsender, broken down by class. It also shows - for each
> contributor - how the horizon would shift if that holder were
> removed.
>
> Shinya said [1] that we could have a view in the future. We could
> have both the logging and the view call a single function that reads
> the procArray and other sources to gather the horizon information. I
> think the logging and the view would complement each other.
>
> Should I start another thread?
My mild preference would be to keep the discussion on this thread,
since the shared function design is central to both the log and the
view and may be easier to keep aligned in one place. That said, I'm
not strongly attached to that, so please pick whichever feels more
convenient.
--
Best regards,
Shinya Kato
NTT OSS Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2026-06-03 01:25:01 | Re: Eager aggregation, take 3 |
| Previous Message | Shinya Kato | 2026-06-03 01:11:01 | Re: Report oldest xmin source when autovacuum cannot remove tuples |