Re: Impact of multixact "members" limit exceeded

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Daniel Lagerman <spjheruur(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Impact of multixact "members" limit exceeded
Date: 2018-06-14 03:29:01
Message-ID: 20180614032901.wn5xfnizfxnj2q7t@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2018-Jun-13, Daniel Lagerman wrote:

> Hello!
>
> I have a question where I'm trying to determine the seriousness of the
> problem.

What's your server version?

The way to reclaim members space is to move forwards the
pg_database.datminmxid value from the database where it is oldest; and
the way to move *that* forward is to advance the pg_class.relminmxid
value from the tables in which it is oldest. So you need to set a low
value vacuum_multixact_freeze_min_age and _table_age and vacuum those
tables.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message a 2018-06-14 03:34:00 How to reference a composite type in schemas not "public"?
Previous Message Alex O'Ree 2018-06-14 02:16:20 Re: Merging two database dumps