-
Notifications
You must be signed in to change notification settings - Fork 3
MySQL or MariaDB #150
Comments
Concerning the database-'engine' I clearly opt for MariaDB. I see no
reason to go with Oracle.
MySQL vs. Postgres? This is in theory doable *), but would require heavy
changes in the codebase. And a switchable/optional setup is out of
sight, resp. not considered (or?).
But honestly, as long as the actual database design yields to something
that only runs in 30+ GB RAM, this discussion is way pointless. Maybe
try to look at the elephant in the room?
Three tables in mxq, a biggy, two trivials, maybe think of how to move
the finished jobs into a kind of bag-table, and have the active ones
acessible? So, I propose adding an other table, plus some logic. This
will indeed not yield to 'realtime' performance, but would make the
whole thing more responsive and less memory hungry **).
Thomas
*) Yes, stored procedures, datatypes, etc., can all be adjusted...
**) IMHO SQL-databases are intended to be run under constrained/limited
conditions (Well, indeed there is the Hans/Günther way, ... *grinsel*)
Donald Buczek wrote:
… Our instance currently uses MySQL 5.6.14. The documentation for 5.6 is
no longer available on the documentation site 1
<https://dev.mysql.com/doc/refman/8.2/en/> and we've even hit
compatibility problems between 5.6 instance and the 5.7 documentation 2
<#149>. We should update the database engine.
Should we go to MySQL 8 or MariaDB 10? The data files are no longer
binary compatible.
PostgreSQL could be considered to, but it would need a strong argument,
because conversion problems are more likely.
—
Reply to this email directly, view it on GitHub Enterprise
<#150>, or unsubscribe
<https://github.molgen.mpg.de/notifications/unsubscribe-auth/AAAACSJ6WFAVHRBRABVAVWTYL7QU5ANCNFSM2NUH>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign in
to join this conversation on GitHub.
Our instance currently uses MySQL 5.6.14. The documentation for 5.6 is no longer available on the documentation site 1 and we've even hit compatibility problems between 5.6 instance and the 5.7 documentation 2. We should update the database engine.
Should we go to MySQL 8 or MariaDB 10? The data files are no longer binary compatible.
PostgreSQL could be considered to, but it would need a strong argument, because conversion problems are more likely.
The text was updated successfully, but these errors were encountered: