Vacuum backend with backend_xmin?

Поиск
Список
Период
Сортировка
От Torsten Förtsch
Тема Vacuum backend with backend_xmin?
Дата
Msg-id CAKkG4_mX+yO6oigW7YY6rXy0HTFj_bmrQ0_ktcxLKCxDbVaf4Q@mail.gmail.com
обсуждение исходный текст
Ответы Re: Vacuum backend with backend_xmin?
Re: Vacuum backend with backend_xmin?
Список pgsql-general
Дерево обсуждения
Hi,

This is a VACUUM FREEZE process.

-[ RECORD 1 ]------+--------------
pid                | 129471
datid              | 16401
datname            | feed
relid              | 1889166
phase              | scanning heap
heap_blks_total    | 1254901
heap_blks_scanned  | 1017524
heap_blks_vacuumed | 0
index_vacuum_count | 0
max_dead_tuples    | 11184809
num_dead_tuples    | 0
backend_xid        | <NULL>
backend_xmin       | 3267908740
age                | 8572

The query is:

select v.*, a.backend_xid, a.backend_xmin, age(a.backend_xmin)
from pg_stat_progress_vacuum as v join pg_stat_activity as a on a.pid=v.pid

Now, my question is why does a vacuum backend have a backend_xmin? I am just curious.

Thanks,
Torsten

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

Предыдущее
От: Ian van der Linde
Дата:
Сообщение: Question regarding automatically paused streaming replication
Следующее
От: Ron Johnson
Дата:
Сообщение: Escaping single quotes with backslash seems not to work