Simon Riggs <si...@2ndquadrant.com> writes: > Discussing this makes me realise that we need a more useful response > than just "your data is corrupt", so user can respond "yes, I know, > I'm trying to save whats left".
> We'll need a way of expressing some form of corruption tolerance. > zero_damaged_pages is just insane, much better if we set > corruption_tolerance = N to allow us to skip N corrupt pages before > failing, with -1 meaning keep skipping for ever. Settable by superuser > only. Define "skip". Extra points if it makes sense for an index. And what about things like pg_clog pages? regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers