HN

Need help?
<- Back
Postgres SELECT DISTINCT Does Not Scale

Postgres SELECT DISTINCT Does Not Scale

KraftyOne

Comments (20)

  • nattaylor
  • procaryote
    I've generally started to treat use of SELECT DISTINCT as a warning flag, as it's very common that it indicates bad codeSome use it because they don't understand uniqueness constraints and try to fix it in post so to say. Some use it because they forgot a join condition and are absolute amateurs. Some use it because it fixed a problem for them once and now they add it everywhereThese people seem to outnumber the people who use SELECT DISTINCT in a well thought out manner
  • sandeepkd
    It says that the company is co-founded by Postgres creator. I find that bit hard to believe given that there is nothing novel in the article, probably discovery for them. I do understand that everyone has to go through their own journey to learn these things but at the same time when you are running business then seeking professional help isnt a bad idea.Based on my experience queries like these cannot scale, whatever you do. However if you are already on a path where you had invested a lot in such queries then hire a DBA, if you are not far off then hire an architect to model the data for better performance.
  • colenikol2
    [dead]
  • thesuperevil
    [flagged]
  • DiabloD3
    "Postgres SELECT DISTINCT Does Not Scale"Correct. This is documented in depth: DISTINCT sorts the results first.The article's use case seems to imply the author did not know about GROUP BY, nor does it imply the author knew about indexes, nor ANALYZE. Postgres 18's new skip scan indexing also could help here, so ensuring the planner chooses that could help.