4 ms·
Your screenshot for issues found show indices being created with CREATE INDEX. If someone runs that on a prod DB with a large table, they’re gonna have a bad ti
by sgarland 2y ago
Your screenshot for issues found show indices being created with CREATE INDEX. If someone runs that on a prod DB with a large table, they’re gonna have a bad time. You should have it suggest CREATE INDEX CONCURRENTLY.
Also, if I’m being honest, it’s a little off-putting to see a tool giving advice on Postgres and not differentiating between those two.
- j45 2y agoAlways lots to learn, appreciate the insight. It’s interesting that Postgres doesn’t seem to default some of these settings since they are clearly advisable as most cases.
- sgarland 2y agoI’ve long held that Postgres is more powerful than MySQL in terms of flexibility and options, but you really ought to have thoroughly read and understood the manual to run it in prod. In comparison, MySQL does a fantastic job out of the box (modulo buffer pool sizing and sync_array_size, and tbf Postgres is equally bad at the former, and the latter doesn’t matter until larger scale), but is somewhat limited in what you can do with it (emphasis on somewhat – it’s still quite adequate for nearly anyone). That’s why I’m forever salty that all of the tech influencers and bloggers hyped up Postgres so much. Yes, it’s a great RDBMS, but the frontend devs eagerly jumping into it haven’t the slightest clue what they’re getting themselves into.
- bertrandhartwig 2y agoThank you for this advice but the tool is designed to help dev ... before to run on production.
- sgarland 2y agoAnd you don’t think someone would copy/paste what they did on dev or stage onto prod?
- bertrandhartwig 2y agowell my dev teams are using Flyway. So, I may not be reasoning correctly. You’re right, a copy-paste can happen quickly. I will modify the code according to your remark.