Home/ Questions/Q 6103285
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T13:42:42+00:00

The query is basically: SELECT DISTINCT my_table.foo from my_table WHERE… Pretending that I’m 100%

  • 0

The query is basically:

SELECT DISTINCT "my_table"."foo" from "my_table" WHERE...

Pretending that I’m 100% certain the DISTINCT portion of the query is the reason it runs slowly, I’ve omitted the rest of the query to avoid confusion, since it is the distinct portion’s slowness that I’m primarily concerned with (distinct is always a source of slowness).

The table in question has 2.5 million rows of data. The DISTINCT is needed for purposes not listed here (because I don’t want back a modified query, but rather just general information about making distinct queries run faster at the DBMS level, if possible).

How can I make DISTINCT run quicker (using Postgres 9, specifically) without altering the SQL (ie, I can’t alter this SQL coming in, but have access to optimize something at the DB level)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your DISTINCT is causing it to sort the output rows in order to find duplicates. If you put an index on the column(s) selected by the query, the database may be able to read them out in index order and save the sort step. A lot will depend on the details of the query and the tables involved– your saying you “know the problem is with the DISTINCT” really limits the scope of available answers.

    • 0