From: | luis(dot)roberto(at)siscobra(dot)com(dot)br |
---|---|
To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_stat_progress_vacuum empty when running vacuum full |
Date: | 2021-02-12 11:19:37 |
Message-ID: | 2079035951.52789040.1613128777722.JavaMail.zimbra@siscobra.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> De: "Luca Ferrari" <fluca1978(at)gmail(dot)com>
> Para: "pgsql-general" <pgsql-general(at)lists(dot)postgresql(dot)org>
> Enviadas: Sexta-feira, 12 de fevereiro de 2021 8:00:46
> Assunto: pg_stat_progress_vacuum empty when running vacuum full
> Hi all,
> I'm running 11.5 and I'm monitoring pg_stat_progress_vacuum every 2
> seconds, while doing from another connection per-table VACUUMs. Every
> vacuum last 30 or more seconds, so I was expecting to see a record
> within pg_stat_progress_vacuum, but nothing appears if the vacuum is
> full. I suspect this is due to vacuum full performing a side-by-side
> table rewriting, rather than in-place actions against the original
> table, but I'm not sure if this is real reason or if I'm missing
> something.
>
> Thanks,
> Luca
Hi!
I believe VACUUM FULL progress can be monitored via the pg_stat_progress_cluster command: https://www.postgresql.org/docs/current/progress-reporting.html#VACUUM-PROGRESS-REPORTING
From | Date | Subject | |
---|---|---|---|
Next Message | Guy Burgess | 2021-02-12 12:48:42 | Re: PostgreSQL occasionally unable to rename WAL files (NTFS) |
Previous Message | Ian Lawrence Barwick | 2021-02-12 11:17:52 | Re: pg_stat_progress_vacuum empty when running vacuum full |