couldn't you use innodb_file_per_table and not worry about the huge ibdata1 file?
1. Monitoring and administration tools for MySQL are (better?) more polished. 2. WAY easier to find MySQL DBA's vs. PG DBA's 3. More resources in general around MySQL. Whatever problem/issue you have it's out there…
Suggesting a code rewrite w/o any idea of what the code looks like or what the issues are is pretty awful. PHP is a good solution for plenty of projects out there. There are plenty of high revenue operations that run on…
couldn't you use innodb_file_per_table and not worry about the huge ibdata1 file?
1. Monitoring and administration tools for MySQL are (better?) more polished. 2. WAY easier to find MySQL DBA's vs. PG DBA's 3. More resources in general around MySQL. Whatever problem/issue you have it's out there…
Suggesting a code rewrite w/o any idea of what the code looks like or what the issues are is pretty awful. PHP is a good solution for plenty of projects out there. There are plenty of high revenue operations that run on…