=?ISO-8859-2?Q?Sz=FBcs_G=E1bor?= <surrano(at)gmail(dot)com> writes:
> Query is:
> SELECT idopont WHERE muvelet = x ORDER BY idopont LIMIT 1.
Much the best solution for this would be to have an index on
--- perhaps you can reorder the columns of "muvelet_vonalkod_muvelet"
instead of making a whole new index --- and then say
SELECT idopont WHERE muvelet = x ORDER BY muvelet, idopont LIMIT 1
PG 8.1 can apply such an index to your original query, but older
versions will need the help of the modified ORDER BY to recognize
that the index is usable.
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2005-12-21 19:39:35|
|Subject: Re: ORDER BY costs |
|Previous:||From: Michael Fuhr||Date: 2005-12-21 18:51:02|
|Subject: Re: Wrong index used when ORDER BY LIMIT 1|