Re: MultiXactId Error in Autovacuum - Mailing list pgsql-admin

From Albe Laurenz
Subject Re: MultiXactId Error in Autovacuum
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17C5CC73@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: MultiXactId Error in Autovacuum  (Karl Hafner <karl@scoreloop.com>)
Responses Re: MultiXactId Error in Autovacuum  (Karl Hafner <karl@scoreloop.com>)
List pgsql-admin
Karl Hafner wrote:
>> Do you know if you experienced transaction ID wraparound as the
>> message suggests?
> 
> I am not aware of a wraparound in the past. I am quite sure no.
> 
>> Are there any other questionable messages in the log?
> 
> The log shows nothing special except this error that is always associated with the same MultiXactId
> 2683601542.

Well, probably you are right, because PostgreSQL would shutdown
before a wraparound happens, and you would have noticed that.

I don't know how it happened, but your database has suffered
corruption.  Any chance you can restore from a backup?
Can you still "SELECT *" from the table that has the problem?

Yours,
Laurenz Albe

pgsql-admin by date:

Previous
From: Gary Stainburn
Date:
Subject: Re: Postgresql not accessible, recovering
Next
From: Luca Ferrari
Date:
Subject: Re: Postgresql not accessible, recovering