Thank you for your help Alvaro - we really appreciate it.
The error in fact stopped this morning - we took downtime and ran a vacuum
across all of our tables, and saw increased auto vacuum activity as well.
It looks like it bumped up the oldest multitxid to something other than 1 now:
/16, 3:30 PM, "Alvaro Herrera" <alvhe...@2ndquadrant.com> wrote:
>AnandKumar, Karthik wrote:
>> root@site-db01a:/var/lib/pgsql/cmates/data # ls pg_multixact/members
>> 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C
>> 000D 000
ot; <alvhe...@2ndquadrant.com> wrote:
>AnandKumar, Karthik wrote:
>> Hi,
>>
>> We run postgres 9.4.5.
>>
>> Starting this morning, we started seeing messages like the below:
>> Oct 12 14:07:15 site-db01a postgres[11253]: [106430-1]
>> app=,user=,db=,
Hi,
We run postgres 9.4.5.
Starting this morning, we started seeing messages like the below:
Oct 12 14:07:15 site-db01a postgres[11253]: [106430-1] app=,user=,db=,ip=LOG:
MultiXact member wraparound protections are disabled because oldest
checkpointed MultiXact 1 does not exist on disk
Oct 12
