| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Karl Hafner *EXTERN*" <karl(at)scoreloop(dot)com> |
| Cc: | Strahinja Kustudic <strahinjak(at)nordeus(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: MultiXactId Error in Autovacuum |
| Date: | 2013-11-19 14:55:00 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17C5CC73@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2013-11-20 10:57:13 | Re: Postgresql not accessible, recovering |
| Previous Message | Gary Stainburn | 2013-11-19 14:45:23 | Re: Postgresql not accessible, recovering |