On: Postgres scaling advice

[ben509]

Predictably bad won't result in a sudden spike in IO usage that brings down a production system. This is why Oracle has SQL profiles.

[Tostino → ben509]

Then use something like pg_hint_plan: https://pghintplan.osdn.jp/pg_hint_plan.html (never used it myself)

I've been bitten by bad optimizer choices which took way too long to figure out how to debug / fix, so I know the pain. I do hope the PG optimizer continues improving. It's one of the weakest areas in comparison to commercial DB's IMO.