• Julien Muchembled's avatar
    mysql: do not use unsafe TRUNCATE statement · c3c2ffe2
    Julien Muchembled authored
    TRUNCATE was chosen for performance reasons, but it's usually done on small
    tables, and not for performance-critical operations. TRUNCATE commits
    implicitely, so for pt/ttrans in particular, it's certainly slower due to extra
    fsyncs to disk.
    
    On the other side, committing too early can corrupt the database if the storage
    node is stopped just after. For example, a failure in changePartitionTable()
    can cause 'pt' to remain empty.
    c3c2ffe2
Name
Last commit
Last update
neo Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
BUGS.rst Loading commit data...
CHANGELOG.rst Loading commit data...
COPYING Loading commit data...
MANIFEST.in Loading commit data...
README.rst Loading commit data...
TESTS.txt Loading commit data...
TODO Loading commit data...
UPGRADE.rst Loading commit data...
ZODB.patch Loading commit data...
ZODB3.patch Loading commit data...
importer.conf Loading commit data...
neo.conf Loading commit data...
neoadmin Loading commit data...
neoctl Loading commit data...
neolog Loading commit data...
neomaster Loading commit data...
neomigrate Loading commit data...
neostorage Loading commit data...
setup.py Loading commit data...