Re: Impact of multixact "members" limit exceeded - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Impact of multixact "members" limit exceeded
Date
Msg-id 20180614032901.wn5xfnizfxnj2q7t@alvherre.pgsql
Whole thread Raw
In response to Impact of multixact "members" limit exceeded  (Daniel Lagerman <spjheruur@gmail.com>)
Responses Re: Impact of multixact "members" limit exceeded
List 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


pgsql-general by date:

Previous
From: "Alex O'Ree"
Date:
Subject: Re: Merging two database dumps
Next
From: "a"
Date:
Subject: How to reference a composite type in schemas not "public"?