Jeff Davis <pg...@j-davis.com> writes: >> -A relation name >> -Corruption type (an entry from this list) >> -How many blocks to touch >> >> I'll just loop based on the count, randomly selecting a block each time >> and messing with it in that way.
For the messing with it part, did you consider zzuf? http://caca.zoy.org/wiki/zzuf > Does it make sense to have a separate executable (pg_corrupt) just for > corrupting the data as a test? Or should it be part of a > corruption-testing harness (pg_corruptiontester?), that introduces the > corruption and then verifies that it's properly detected? Maybe we need our own zzuf implementation, though. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers