Multixact wraparound monitoring

From: bruno da silva <brunogiovs(at)gmail(dot)com>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Multixact wraparound monitoring
Date: 2023-09-13 12:21:40
Message-ID: CAB+Nuk-70YnDmXSkszHA5_rSgSpX2fYJG7yp36Q5jFz6obuLcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Wyatt Alt 2023-09-14 05:14:28 Re: Multixact wraparound monitoring
Previous Message Thomas Munro 2023-09-13 03:11:13 Re: FW: query pg_stat_ssl hang 100%cpu