9/15/2023 0 Comments Unity with mysql vs postgresqlSimple and fast and "helpful" is a really compelling argument, and part of why it underscores a lot of long-running projects. Adherents of strict type checking or people charged with running down data inconsistencies will strongly disagree that this is a "feature" at all, though. Automatically correcting common or simple errors was super convenient for small developers in the late 1990s, early 2000s. It also was more permissive about incorrect types and automatic type conversions (still is, I believe). MySQL was missing a lot of functionality, like transactions, but was really simple and blazing fast. Twenty years ago, Postgres was powerful but comparatively heavy. Maybe one day pgsql will be a silver bullet for all projects, but for now I don't think so. In other project with simpler queries we choose mysql because maintenance stops will kill our SEO. In our actual project we need to stop psql once per month to exec full vacuum (autovacum can't run because we have a lot of writes and wraparound problem is a real problem for us), but mysql can't run our complex queries without die. Read commited as default instead mysql repeteable read isolation as default.īut I hate write custom failover scripts (data copy, stonish, choose replication method, failover trigger.) that can be buggy and had data losses and outages.įor me mysql is easier to maintain, but for some problems mysql is a no go. For some problems I prefer percona clusters (mysql) over pgsql ones.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |