On 1/7/12 5:26 AM, Heikki Linnakangas wrote:
Perhaps there needs to be a third setting, calculate-but-dont-verify, where CRCs are updated but existing CRCs are not expected to be correct. And a utility to scan through your database and fix any incorrect CRCs, so that after that's run in calculate-but-dont-verify mode, you can safely turn checksums on.
The users of any feature like this are eventually going to demand a "scrubbing" utility that validates the checksums in a background task. Doing something like pg_dump just to validate your copy of the data is still clean is not a great approach. If you accept that sort of utility is inevitable, you might as well presume it could handle this sort of task eventually too.
-- Greg Smith 2ndQuadrant US g...@2ndquadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
