Re: VACUUM PANIC: corrupted item pointer
От | André Volpato |
---|---|
Тема | Re: VACUUM PANIC: corrupted item pointer |
Дата | |
Msg-id | 48F8CE6C.3040702@ecomtecnologia.com.br обсуждение исходный текст |
Ответ на | Re: VACUUM PANIC: corrupted item pointer (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
Tom Lane escreveu: > =?ISO-8859-1?Q?Andr=E9_Volpato?= <andre.volpato@ecomtecnologia.com.br> writes: > >> 8. Postgres is up, but... >> # psql matriz >> psql: FATAL: could not read block 0 of relation 1664/0/2676: read only >> 0 of 8192 bytes >> > > Looks like your raid array is dying under you :-( ... We hope it last more 3 weeks, new servers are coming... > 2676 is pg_authid_rolname_index, so you could probably get around that > particular problem by reindexing pg_authid in standalone mode. (You > might need to use the -P option too, not sure.) But the "corrupted item > pointer" complaint is heap corruption and no amount of reindexing will > fix it. > Since you seem to be able to select from the broken table without > problem, I'd suggest just copying its data into a new table and dropping > the broken one (or truncate it and copy the data back). > Not anymore... I cant even connect to any database since reboot (#7). I tryed to restore global/ directory from backup, and I got "cache lookup failed for database 87421438". Now we ran initdb again, and start recreating dbs with backup data. > regards, tom lane > -- []´s, ACV
В списке pgsql-general по дате отправления: