Multixact wraparound monitoring

Поиск
Список
Период
Сортировка
От bruno da silva
Тема Multixact wraparound monitoring
Дата
Msg-id CAB+Nuk-70YnDmXSkszHA5_rSgSpX2fYJG7yp36Q5jFz6obuLcw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Multixact wraparound monitoring  (Wyatt Alt <wyatt.alt@gmail.com>)
Re: Multixact wraparound monitoring  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-performance
Hello.

I just had an outage on postgres 14 due to multixact members limit exceeded.

So the documentation says "There is a separate storage area which holds the list of members in each multixact, which also uses a 32-bit counter and which must also be managed."

Questions:
having a 32-bit counter on this separated storage means that there is a global limit of multixact IDs for a database OID?

Is there a way to monitor this storage limit or counter using any pg_stat table/view?

are foreign keys a big source of multixact IDs so not recommended on tables with a lot of data and a lot of churn? 

Thanks

--
Bruno da Silva

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

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Planning time is time-consuming
Следующее
От: Wyatt Alt
Дата:
Сообщение: Re: Multixact wraparound monitoring