| From: | Karl Hafner <karl(at)scoreloop(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| 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-20 14:20:48 |
| Message-ID: | CA+MJ4cQgKy6q0AQXrT_+DbyYZxoJ12ci51wLrid2FFo=9XfdLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> 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?
>
I cannot run a full SELECT * on that table. It stops after a few minutes
with the same error.
I am currently testing different things on a DB created from a backup like
exporting per month/per day …
but I am running into this error again and again.
Running a VACUUM --FULL gives me: WARNING: concurrent delete in progress
within table "the_bad_table" … then it also breaks.
BR,
Karl
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Burgholzer | 2013-11-21 12:34:39 | Archive fails due to missing backup file |
| Previous Message | Luca Ferrari | 2013-11-20 10:57:13 | Re: Postgresql not accessible, recovering |