5 files changed, 0 insertions, 35 deletions
diff --git a/docs/manpages/tracker-info.1 b/docs/manpages/tracker-info.1
index f50759398..fbbc68fac 100644
--- a/docs/manpages/tracker-info.1
+++ b/docs/manpages/tracker-info.1
@@ -72,13 +72,6 @@ approach you can use if you want to \fIwrite\fR to the database.
 With "\fBauto\fR" the backend is decided for you, much like it would
 be if this environment variable was undefined.
 
-.TP
-.B TRACKER_PRAGMAS_FILE
-Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
-With this environment variable pointing to a text file you can override these
-settings. The file is a \\n separated list of SQLite queries to execute on any
-newly created SQLite connection in \fBtracker-store\fR.
-
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-sparql (1).
diff --git a/docs/manpages/tracker-search.1 b/docs/manpages/tracker-search.1
index 109602ed0..06762f5af 100644
--- a/docs/manpages/tracker-search.1
+++ b/docs/manpages/tracker-search.1
@@ -129,13 +129,6 @@ approach you can use if you want to \fIwrite\fR to the database.
 With "\fBauto\fR" the backend is decided for you, much like it would
 be if this environment variable was undefined.
 
-.TP
-.B TRACKER_PRAGMAS_FILE
-Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
-With this environment variable pointing to a text file you can override these
-settings. The file is a \\n separated list of SQLite queries to execute on any
-newly created SQLite connection in tracker-store.
-
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-stats (1),
diff --git a/docs/manpages/tracker-sparql.1 b/docs/manpages/tracker-sparql.1
index cf60f9fee..78ea98971 100644
--- a/docs/manpages/tracker-sparql.1
+++ b/docs/manpages/tracker-sparql.1
@@ -236,13 +236,6 @@ approach you can use if you want to \fIwrite\fR to the database.
 With "\fBauto\fR" the backend is decided for you, much like it would
 be if this environment variable was undefined.
 
-.TP
-.B TRACKER_PRAGMAS_FILE
-Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
-With this environment variable pointing to a text file you can override these
-settings. The file is a \\n separated list of SQLite queries to execute on any
-newly created SQLite connection in \fBtracker-store\fR.
-
 .SH EXAMPLES
 .TP
 List all classes
diff --git a/docs/manpages/tracker-store.1 b/docs/manpages/tracker-store.1
index 77ecb177f..28452f0da 100644
--- a/docs/manpages/tracker-store.1
+++ b/docs/manpages/tracker-store.1
@@ -75,13 +75,6 @@ number represents the number of cached statements to keep around.
 This environment variable is used mainly for testing purposes.
 
 .TP
-.B TRACKER_PRAGMAS_FILE
-Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
-With this environment variable pointing to a text file you can override these
-settings. The file is a \\n separated list of SQLite queries to execute on any
-newly created SQLite connection in tracker-store.
-
-.TP
 .B TRACKER_USE_LOG_FILES
 Don't just log to stdout and stderr, but to log files too which are
 kept in $HOME/.local/share/tracker/. This came into effect in 0.15.3
diff --git a/docs/manpages/tracker-tag.1 b/docs/manpages/tracker-tag.1
index b450f8f24..c4e3285e5 100644
--- a/docs/manpages/tracker-tag.1
+++ b/docs/manpages/tracker-tag.1
@@ -97,13 +97,6 @@ approach you can use if you want to \fIwrite\fR to the database.
 With "\fBauto\fR" the backend is decided for you, much like it would
 be if this environment variable was undefined.
 
-.TP
-.B TRACKER_PRAGMAS_FILE
-Tracker has a fixed set of PRAGMA settings for creating its SQLite connection.
-With this environment variable pointing to a text file you can override these
-settings. The file is a \\n separated list of SQLite queries to execute on any
-newly created SQLite connection in \fBtracker-store\fR.
-
 .SH SEE ALSO
 .BR tracker-store (1),
 .BR tracker-sparql (1),