From: | "Pavlov, Vladimir" <Vladimir(dot)Pavlov(at)tns-global(dot)ru> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Multixacts wraparound monitoring |
Date: | 2016-03-24 07:54:25 |
Message-ID: | B38B34EC5621E34DABCE13E8B18936E602DC2C14BE57@EXSERV.Gallup.tns |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
How can we determine when an error of approximation multixacts wraparound?
According to the information from pg_class:
select datname,datminmxid from pg_database;
datname | datminmxid
----------------+------------
template1 | 347462426
template0 | 347462426
postgres | 347462426
zabbix | 467261307
db_3 | 291141939
db_1 | 388282963
db | 388282963
But when the vacuum/autovacuum starts up, an error occurs:
WARNING: oldest multixact is far in the past
HINT: Close open transactions with multixacts soon to avoid wraparound problems.
If I understand correctly, approaching Multixact member wraparound.
But how to understand when it comes exactly and what to do?
PostgreSQL version - 9.3.10, OS Debian 7.8.
Thank you.
Sorry, if I chose the wrong mailing list.
Kind regards,
Vladimir Pavlov
From | Date | Subject | |
---|---|---|---|
Next Message | Moreno Andreo | 2016-03-24 09:46:45 | Re: PostgreSQL crash with PANIC message |
Previous Message | Michael Paquier | 2016-03-24 04:12:00 | Re: PostgreSQL crash with PANIC message |