diff options
author | fox <[email protected]> | 2018-08-31 07:32:23 +0000 |
---|---|---|
committer | fox <[email protected]> | 2018-08-31 07:32:23 +0000 |
commit | 7742eb87f68dd6305b10a168bd0ccf7ae5173ead (patch) | |
tree | 6b52156c3e85c34a99b2b2bbdce955e4b2a03f1d | |
parent | e638379a410f52ab514b214b758afd39b7a1d9e7 (diff) |
Update page 'FAQ'
-rw-r--r-- | FAQ.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -22,7 +22,7 @@ If that is too much effort you will have to enter your login and password again #### What should I use - MySQL or PostgreSQL?
In general, tt-rss is written with PostgreSQL in mind. While MySQL backend is maintained and supported, some optional
-features (like fast full-text search) or plugins may be PostgreSQL-exclusive. Postgres should also give you
+features (like fast full-text search) or plugins may be Postgres-exclusive. Postgres should also give you
much better performance, especially if you tune it a bit.
TLDR: use PostgreSQL if you can, otherwise use MySQL. In the end, tt-rss is completely functional on both databases.
|