mem0 Configuration only supports history_db_path — does this mean MySQL / PostgreSQL are not supported for history storage?

I noticed in the current configuration that only the history_db_path parameter is provided, which seems to indicate that history data is stored using a local file-based database (e.g., SQLite).

I'd like to confirm whether MySQL or PostgreSQL are currently not supported as backends for storing historical data. If that's the case, is there any plan to support these relational databases in the future?

Jul 04 '25 04:07 homejim

@homejim Currently it only supports SQLite which is file based only. For supporting Postgres or any other you might have to write your own custom class.

Jul 04 '25 05:07 Jainish-S

@homejim Currently it only supports SQLite which is file based only. For supporting Postgres or any other you might have to write your own custom class.

The cloud version, it shouldn't be using SQLite, right? So are there two different versions code? @Jainish-S

Jul 04 '25 10:07 homejim

Just to confirm, since it’s been about three months, does mem0 history still only support SQLite?

Oct 29 '25 10:10 michaelact