| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(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-06-29 15:31:03 |
| Message-ID: | CAA5RZ0vEQ8aykyuoHRuyD=F+JhGEa0Zfy2vgVoEXtJfkt0Pt-A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> ComputeXidHorizons() already takes ProcArrayLock and has all the
> information about who is blocking the vacuum, so I think we can
> capture the blocker right there and get the reason almost for free,
> without a second scan.
This idea proved to result in incorrect information. See [1]
--
Sami Imseih
Amazon Web Services (AWS)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2026-06-29 15:31:12 | Re: Report index currently being vacuumed in pg_stat_progress_vacuum |
| Previous Message | Bharath Rupireddy | 2026-06-29 15:22:50 | Re: Report oldest xmin source when autovacuum cannot remove tuples |