Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparentwraparound
От | Moreno Andreo |
---|---|
Тема | Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparentwraparound |
Дата | |
Msg-id | 409a55a4-e380-e5e4-a1a4-d7e69b50ab98@evolu-s.it обсуждение исходный текст |
Ответ на | Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparentwraparound (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Список | pgsql-general |
Hi Alvaro, sorry for late reply, I've been out of office. Il 09/10/19 19:51, Alvaro Herrera ha scritto: > On 2019-Oct-07, Moreno Andreo wrote: > >> Unfortunately, it didn't work :( >> >> db0=# select * from failing_table where ctid='(3160,31)' for update; >> ERROR: MultiXactId 12800 has not been created yet -- apparent wraparound > Oh well. It was a long shot anyway ... It was a long shot, but it was worth trying >> Since the probability we are into corruption is very high, what if I \copy >> all the table but the failing row(s) to an external file, drop and recreate >> the table, and then \copy clean data back inside? > Yes, that should work. It did not work... I think there was some big deal with the cluster itself. To extract these small parts of data I had to SELECT using OFFSET and LIMIT. Well, the same query (i.e. select * from table offset 35 limit 145) run as it is worked well, but from the moment I put it into a COPY statement, it was messing again with multixact, even if I tried back the only query. It ended recovering data from backups (2 days old, and that's good news) Thanks for your time Moreno.- >
В списке pgsql-general по дате отправления: