Dne 20.4.2011 22:11, Tomas Vondra napsal(a):
> There's a very nice guide on how to do that
>
> http://blog.endpoint.com/2010/06/tracking-down-database-corruption-with.html
>
> It sure seems like the problem you have (invalid alloc request etc.).
> The really annoying part is locating the block, as you have to scan
> through the table (which sucks with such big table).
>
> And yes, if there's corruption, there might be more corrupted blocks.
BTW, there's a setting 'zero_damaged_pages' that might help with this
http://www.postgresql.org/docs/8.2/static/runtime-config-developer.html
see this talk for more details how to use it
http://www.casitconf.org/casitconf11/Tech_track_2_files/cascadia_postgres_rbernier.pdf
Anyway don't play with this without the file backup, as this will zero
the blocks.
Tomas