Re: empty pg_stat_progress_vacuum

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: empty pg_stat_progress_vacuum
Дата
Msg-id Y2C2VNE3vCUbvzCc@paquier.xyz
обсуждение исходный текст
Ответ на empty pg_stat_progress_vacuum  (senor <frio_cervesa@hotmail.com>)
Список pgsql-general
On Fri, Oct 21, 2022 at 10:21:23PM +0000, senor wrote:
> I'm mainly wanting to understand why I'm not seeing processes in
> pg_stat_progress_vacuum. If I rapidly refresh I occasionally see an
> entry for a very small table. A manually started vacuum didn't show
> up either.

It may be possible that the run is short enough that it did not get
captured, as pg_stat_progress_vacuum is a snapshot of the current
point in time.

> Pg version 11.4

Hard to say, but I think that you should update your binaries, at
least.  11.4 has been release in June 2019, and the latest release
available is 11.17, meaning that you are missing more than three years
worth of bug fixes.  Based on the roadmap in [1], 11.18 should be out
next week.

[1]: https://www.postgresql.org/developer/roadmap/
--
Michael

Вложения

В списке pgsql-general по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"
Следующее
От: Laurenz Albe
Дата:
Сообщение: Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"