Re: table corrupted

2009/10/23 João Eugenio Marynowski <joaoem(at)gmail(dot)com>

> I thought this would solve my problems but not yet ...
> the block that I found is not presenting error...
> find_bad_block
> ----------------
> (514708,16)
> (1 registro)
> blockId / blocks_per_chunk = 514708 / 131072 = 3,9269104
> base/21058/21271.3
> chunk_block_id = block_id % blocks_per_chunk = 514708 % 131072 = 121492
> is attached the result of pg_filedump -if -R 121492
> /var/lib/postgresql/8.2/main/base/21058/21271.3
> Even then I filled the block with zero
> But when I run again the find_bad_block it show one block before, ctid
> 514707, and then, 514706 and I stop...
> Any suggestion and explication?
>
> --
> João Eugenio
>

I fond manually a record with error (462813,13) and zeroed it and the BD
work ok only with 18 register lost that will be recovery from old backup.
The function find_bad_block (
http://archives.postgresql.org/pgsql-general/2007-07/msg00506.php )
don't work for me, anybody know why?

Thanks for now!

--
João Eugenio Marynowski