Postgres is eating the database world

Re:Postgres is eating the database world by hipadev23 on Friday March 15, 2024 @12:50AM (#39712163)

MySQL offers this via use/force index (…). Similar problem where the QP will inexplicably decide one day to make a query really slow and you gotta override it.

[ Parent | on HN ]

Re:Postgres is eating the database world by donatj on Friday March 15, 2024 @12:57AM (#39712195)

We have a couple queries where using the correct index they'll take milliseconds, using the wrong index it'll take minutes - and mysql occasionally enough to be a noticeable load on the database chooses the wrong one and we've specified "USE INDEX" even though I really hate having to do so.

[ Parent | on HN ]

Re:Postgres is eating the database world by Minor49er on Friday March 15, 2024 @01:02AM (#39712212)

I'm curious about the query and schema that you're using

[ Parent | on HN ]