The xf_search_index table can be truncated if using XFES

P

Paul B

XenForo moderator
Staff member
For those of you who aren't aware, if you're using XFES you can truncate the xf_search_index table, as it is no longer used.

On a large site, that will reduce the DB size by a considerable amount, (potentially) resulting in less server space being utilised, quicker backups, etc.

phpMyAdmin
Code: 
TRUNCATE 'xf_search_index';

SSH
Code: 
TRUNCATE TABLE xf_search_index;
 
Last edited:
@Slavik, @Brogan: I have a question about xf_search table usage. Even if I use Elasticsearch with XES 1.0.3, it still create new entries into xf_search table when I perform a search... is this normal?
Code: 
MariaDB [axivo]> truncate table xf_search;
Query OK, 0 rows affected (0.22 sec)
### Search performed on website...
MariaDB [axivo]> select search_id, result_count from xf_search;
+-----------+--------------+
| search_id | result_count |
+-----------+--------------+
|         1 |           22 |
+-----------+--------------+
First, I thought is related to new http.jsonp.enable setting but even with it commented I still get search entries into table. I guess is for caching purposes so it returns the result directly from table? It should not IMO.
Code: 
# curl localhost:9200
{
  "status" : 200,
  "name" : "Tutinax the Mountain-Mover",
  "version" : {
    "number" : "1.3.1",
    "build_hash" : "2de6dc5268c32fb49b205233c138d93aaf772015",
    "build_timestamp" : "2014-07-28T14:45:15Z",
    "build_snapshot" : false,
    "lucene_version" : "4.9"
  },
  "tagline" : "You Know, for Search"
}
 
Last edited:
You must log in or register to reply here.

Similar threads

The Grand Potentate
  • Question Question
XF 1.3 What causes the xf_search_index table to crash?
Replies
6
Views
1K
AndyB
AndyB
Back
Top Bottom