I hope, I've solved it.
I found 512 damaged bytes on the 29th 8k page of the pg_type's datafile
($PGDATA/base/16390/1247), it was overwritten by text from some log(?!).
When I had dropped the whole 8k page (dd of=/tmp/head count=29 bs=8192,
dd of=/tmp/tail skip=30 bs=8192, then cat /tmp/head /tmp/tail), the
pg_dumpall utility was able to dump the DB instance then.
I compared schemas (pg_dumpall -s), fortunately only several empty, not
used tables were affected.
Then I imported the dump, and now the DB instance seems to work properly,
also the pg_dumps, vacuum anylysis.
Best regards,
Filip Krska
--
ComSTAR spol. s r. o.
Třebohostická 14
100 31 Praha 10
HotLine (pev.): 274 016 000
HotLine (mob.): 777 343 857
On Fri, 6 Jun 2008, Alvaro Herrera wrote:
Filip Krška wrote:
Hello,
we have (maybe due to temporary Disk Array HW failure, which occurred on
the same day the pg_dump started to complain - array is now successfully
rebuilt) problem with consistency of pg_catalog.pg_type table.
Did you solve this problem?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
