Re: preventing ERROR: multixact "members" limit exceeded - Mailing list pgsql-general

From Steve Kehlet
Subject Re: preventing ERROR: multixact "members" limit exceeded
Date
Msg-id CA+bfosEx6MLL1zXWiwvic7odDiFD_7qW8d7VnUE3LiL1QERfAA@mail.gmail.com
Whole thread Raw
In response to Re: preventing ERROR: multixact "members" limit exceeded  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
On Tue, May 17, 2016 at 10:40 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
In 9.4, not really. In 9.5 there's a function mxid_age() that gives you
the age of a multixact, so you'd grab the oldest from
pg_database.datminmxid and compute the age of that one.  Going from the
oldest multi to the oldest offset cannot be done without an additional
function, however.  It's much easier to keep track of the oldest file in
$PGDATA/pg_multixact/members/; what you really need to care about is the
size of the "hole" between the newest and the oldest files there.  Once
newest starts to stomp on oldest, you're screwed.

Thank you Alvaro. We're beginning to plan our rollout of 9.5.
 

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: FIRST_VALUE argument must appear in group by?
Next
From: Lucas Possamai
Date:
Subject: Re: Increased I/O / Writes