Re: preventing ERROR: multixact "members" limit exceeded

From: Steve Kehlet <steve(dot)kehlet(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Forums postgresql <pgsql-general(at)postgresql(dot)org>
Subject: Re: preventing ERROR: multixact "members" limit exceeded
Date: 2016-05-17 01:57:26
Message-ID: CA+bfosHXSoVC0o3j-ic2T_nDUoPHRte=vtf9xMsd6s7upWeN_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, May 16, 2016 at 6:18 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> Not really. Your best bet is to reduce the
> autovacuum_multixact_freeze_min_age limit, so that vacuums are able to
> get rid of multixacts sooner (and/or reduce
> autovacuum_multixact_freeze_table_age, so that whole-table vacuuming
> takes place earlier).

Thank you very much. I will adjust those settings. Is there a way,
something similar to keeping an eye on `age(relfrozenxid)`, that I can
watch this and keep an eye on it before it becomes a problem?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Guyren Howe 2016-05-17 03:01:31 FIRST_VALUE argument must appear in group by?
Previous Message Vik Fearing 2016-05-17 01:31:30 Re: WAL files not being recycled