Re: MultiXactId Error in Autovacuum
| От | Karl Hafner |
|---|---|
| Тема | Re: MultiXactId Error in Autovacuum |
| Дата | |
| Msg-id | CA+MJ4cQgKy6q0AQXrT_+DbyYZxoJ12ci51wLrid2FFo=9XfdLg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: MultiXactId Error in Autovacuum (Albe Laurenz <laurenz.albe@wien.gv.at>) |
| Ответы |
Re: MultiXactId Error in Autovacuum
|
| Список | 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
В списке pgsql-admin по дате отправления: