Re: preventing ERROR: multixact "members" limit exceeded

Поиск
Список
Период
Сортировка
От Steve Kehlet
Тема Re: preventing ERROR: multixact "members" limit exceeded
Дата
Msg-id CA+bfosEx6MLL1zXWiwvic7odDiFD_7qW8d7VnUE3LiL1QERfAA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: preventing ERROR: multixact "members" limit exceeded  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список 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 по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: FIRST_VALUE argument must appear in group by?
Следующее
От: Lucas Possamai
Дата:
Сообщение: Re: Increased I/O / Writes