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 20:04:34 |
Message-ID: | CA+bfosEx6MLL1zXWiwvic7odDiFD_7qW8d7VnUE3LiL1QERfAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 17, 2016 at 10:40 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Lucas Possamai | 2016-05-17 22:56:18 | Re: Increased I/O / Writes |
Previous Message | David G. Johnston | 2016-05-17 18:10:58 | Re: FIRST_VALUE argument must appear in group by? |