keith has uploaded this change for review.

View Change

Turn off secure_delete in sqlite

libsqlite3 that ships with some distributions may have secure_delete
activated by default. This means all database records are overwritten with
zeros on DELETE. We don't needs this extra overhead.

Change-Id: I9da6499a38096c8df2025bb9d35ec789864b7c5e
---
M src/libmsc/db.c
1 file changed, 6 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-msc refs/changes/41/28341/1

diff --git a/src/libmsc/db.c b/src/libmsc/db.c
index ea0fef3..b310fae 100644
--- a/src/libmsc/db.c
+++ b/src/libmsc/db.c
@@ -585,6 +585,12 @@
 		sqlite3_free(err_msg);
 		/* non-fatal */
 	}
+	rc = sqlite3_exec(g_dbc->db, "PRAGMA secure_delete=0;", 0, 0, &err_msg);
+	if (rc != SQLITE_OK) {
+		LOGP(DDB, LOGL_ERROR, "Unable to disable SECURE_DELETE: %s\n", err_msg);
+		sqlite3_free(err_msg);
+		/* non-fatal */
+	}
 	rc = sqlite3_exec(g_dbc->db, "PRAGMA temp_store=MEMORY;", 0, 0, &err_msg);
 	if (rc != SQLITE_OK) {
 		LOGP(DDB, LOGL_ERROR, "Unable to set TEMP_STORE: %s\n", err_msg);

To view, visit change 28341. To unsubscribe, or for help writing mail filters, visit settings.