logoalt Hacker News

throwatdem12311today at 3:30 AM2 repliesview on HN

Every single time I’ve thought I’ve needed to try these it made it worse.

Every time Claude tries to tell me to try these, it made it worse.

Not once has it made it better for me. I’m doing materialized view refreshes with a billion rows, which is small enough maybe that this doesn’t come into play…but so far the planner knows best.

If the database can’t make it fast with just smart joins and filtering then it’s the architecture that’s a problem, not the database.

Usually the only thing I need to do is increase work_mem.


Replies

silon42today at 4:35 AM

The hints are needed when you have a web scale / online transaction processing application, where you want to guarantee no table scan ever. Ideally, I'd want to rrun without statistics on the tables in that case (ie, no smart joins).

show 2 replies
skywhoppertoday at 10:22 AM

“I’ve never run into it so it can’t be a problem for other people” is an interesting take.