3 ms·
There's one very important reason that I always return to MySQL: - If something goes wrong at 3am, I know how to fix it. Whether it's performance, server setu
by mootothemax 12y ago
There's one very important reason that I always return to MySQL:
- If something goes wrong at 3am, I know how to fix it.
Whether it's performance, server setup, or weird edge cases, I have it covered.
This being the sole reason, does anyone have any "when you're in trouble" guides for Postgres or others?