On 22.11.2017 20:39, ray wrote:
I have reviewed the tickets on the Trac site and the messages in this
forum to see if there are any reliability or installation issues for a
new installation.
How might I find out about trade-offs between the DB options?
SQLite:
+Basically the default. So this probably gets tested the most, and the
most plugins work with this.
+Very simple to set up. (You don't have to do or install anything.)
-Reportedly it gets slow when you have a large number of concurrent
users, and you might even get lock errors.
PostgreSQL:
-Not the default. So some plugins might not be compatible with this just
because nobody ever tested it.
-You need to set it up and configure it separately. So this is one more
thing to learn about.
+Basically the recommended solution if you get performance problems /
lock errors due to many concurrent users.
MySQL:
More or less the same points apply as with PostgreSQL.
But there seem to be more compatibility problems (due to limited key
sizes, limited string sizes, unsuitable default encodings, old storage
engines etc.).
Basically not recommended, unless you have some unrelated reason for
using it. (E.g. you already use MySQL for other systems and just prefer
to do everything with MySQL.)
This is just my impression from what I read. SQLite works fine for me. I
never really used MySQL or PostgreSQL for Trac in production.
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
