3 ms·
MySQL has some aggregation performance over postgres. Having done a recent migration of an application two things that come to mind are: - its case insensitive
by Topgamer7 3y ago
MySQL has some aggregation performance over postgres. Having done a recent migration of an application two things that come to mind are:
- its case insensitive by default, which can make filtering simpler, without having to deal with a duplicate column where all values are lower/upper cased.
- MySQL implements loose index scan and index skip scan, which improves performance of a number of join aggregation operations (https://wiki.postgresql.org/wiki/Loose_indexscan https://wiki.postgresql.org/wiki/Loose_indexscan)
- dpratt 3y ago| its case insensitive by default This is obviously up for debate, but subjectively I find this to be an absolutely terrible design decision.
- hu3 3y agoI agree it's debatable. And not intuitive at first. With that said, in all my years and thousands of tables across multiple jobs, I have yet to see a single case where I had to change a table to be case sensitive. So I guess for me it is a sensible default.