From 55c17b9d8ec81f09a9e242926d9a074497dd2eeb Mon Sep 17 00:00:00 2001 From: Ben Johnson Date: Sun, 6 Jun 2021 09:12:29 -0600 Subject: [PATCH] Move WAL checksum validation message to trace logging Checksum mismatch can regularly occur now that write locks have been removed during WAL sync. This does not pose any corruption risk but does sound scary to end users. Moving this to trace logging instead. --- db.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/db.go b/db.go index e71d6b4..dd33d7e 100644 --- a/db.go +++ b/db.go @@ -1058,7 +1058,7 @@ func (db *DB) copyToShadowWAL(filename string) (newSize int64, err error) { chksum0, chksum1 = Checksum(bo, chksum0, chksum1, frame[:8]) // frame header chksum0, chksum1 = Checksum(bo, chksum0, chksum1, frame[24:]) // frame data if chksum0 != fchksum0 || chksum1 != fchksum1 { - log.Printf("copy shadow: checksum mismatch, skipping: offset=%d (%x,%x) != (%x,%x)", offset, chksum0, chksum1, fchksum0, fchksum1) + Tracef("%s: copy shadow: checksum mismatch, skipping: offset=%d (%x,%x) != (%x,%x)", db.path, offset, chksum0, chksum1, fchksum0, fchksum1) break }