Since the primary use case here seems to be offline analysis and it may not be of much interest to mediawiki users outside of wmf, can we store the checksums in new tables (i.e. revision_sha1) instead of running large alters, and implement the code to generate checksums on new edits via an extension?
Checksums for most old revs can be generated offline and populated before the extension goes live. Since nothing will be using the new table yet, there'd be no issues with things like gap lock contention on the revision table from mass populating it. On Mon, Sep 19, 2011 at 12:10 PM, Brion Vibber <br...@pobox.com> wrote: > [snip] > > So just FYI -- the only *actual* controversy that needs to be discussed in > this thread is "how do we make this update applicable in a way that doesn't > disrupt live sites with many millions of pages?" > > We're pretty fixed on SHA-1 as a checksum sig (already using it elsewhere) > and have no particular desire or need to change or think about > alternatives; > bikeshedding details of the formatting and storage are not at issue. > > -- brion > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
