| From: | Sbob <sbob(at)quadratum-braccas(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | vacuum process running for more than 2 days, still in scanning heap phase |
| Date: | 2025-11-12 18:09:36 |
| Message-ID: | 0a1745be-c54d-43b9-a90f-71e4c721c17c@quadratum-braccas.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
All;
We have a vacuum process that has been running for 2 days, the table is
12GB in total size and vacuum_cost_delay is at 0
The process shows as active in pg_stat_activity, and pg_blocking_pids
returns no blockers
select pg_blocking_pids(1581295);
pg_blocking_pids
------------------
{}
(1 row)
A select from from pg_stat_progress_vacuum where pid = 1581295; shows
the phase as 'scanning heap' and the heap_blks_total, heap_blks_scanned,
max_dead_tuples and num_dead_tuples have shown the same values for at
least the past hour
pid | 1581295
datid | 16398
datname | prod_server_1
relid | 22532
phase | scanning heap
heap_blks_total | 571437
heap_blks_scanned | 344577
heap_blks_vacuumed | 0
index_vacuum_count | 0
max_dead_tuples | 155388267
num_dead_tuples | 199013
We actually tried a pg_terminate_backend on it and it does not die
Thanks in advance for any advice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-11-12 18:26:59 | Re: vacuum process running for more than 2 days, still in scanning heap phase |
| Previous Message | Ron Johnson | 2025-11-12 16:11:56 | Re: pg_dump -j |