Re: could not read block 77 of relation 1663/16385/388818775
От | Darren Reed |
---|---|
Тема | Re: could not read block 77 of relation 1663/16385/388818775 |
Дата | |
Msg-id | 49A1D694.9020904@fastmail.net обсуждение исходный текст |
Ответ на | Re: could not read block 77 of relation 1663/16385/388818775 (Gregory Stark <stark@enterprisedb.com>) |
Список | pgsql-bugs |
Gregory Stark wrote: > Darren Reed <darrenr+postgres@fastmail.net> writes: > > >> ERROR: could not read block 1 of relation 1664/0/1233: read only 0 of >> 8192 bytes >> > > FWIW this is pg_shdepend_reference_index which is actually a bit special. It's > a "shared" relation which means it spans all your databases. Your reindex > didn't rebuild to. To reindex it you would have to shut down postgres and run > REINDEX in postgres in "standalone" mode. > > >> I suppose the logical thing for me to do is go back to 8.2.6. >> > > I think it would be more interesting to know how you got into this situation. > When you ran initdb did anything unusual happen? Is it possible anything later > truncated these files? > Nope. For me it has been very reproducible: - init the database - restore tables from dump files - create indexes for those tables - insert some records using perl DBI - receive above error message My current logifile goes like this: - database startup - create tables creating implicit keys - lots of checkpoints happening too quick (restores) - 3 insert errors due to syntax - 2 EOFs from clients - ERROR could not read block 1 of relation... I haven't even run any queries. The single-user mode REINDEX did fix it, thanks. Darren
В списке pgsql-bugs по дате отправления: