[BUGS] Re: Query planner skipping index depending on DISTINCT parameterorder (2)

Поиск
Список
Период
Сортировка
От Greg Stark
Тема [BUGS] Re: Query planner skipping index depending on DISTINCT parameterorder (2)
Дата
Msg-id CAM-w4HPhUKkB6uA5vSOxZRUenACj-qAbSrcEBdmB1x1PyJ7hYA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [BUGS] Query planner skipping index depending on DISTINCT parameter order (2)  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы [BUGS] Re: Query planner skipping index depending on DISTINCT parameterorder (2)  (Дилян Палаузов<dilyan.palauzov@aegee.org>)
[BUGS] Re: Query planner skipping index depending on DISTINCT parameterorder (2)  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Список pgsql-bugs
On 17 September 2017 at 18:15, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> For plain DISTINCT, yeah we could consider other orderings ... but
> we're rather unlikely to find an index that matches all the output
> columns, regardless of what order they're in.  So it's just not that
> exciting.

I don't follow this part. Are you saying a simple "select distinct a,b
from table" is unlikely to find a matching index on <b,a>? Don't we
already do exactly this for "select a,b from table group by a,b"? I
would have expected the two equivalent SQL statements to use exactly
the same infrastructure and thought it was only a matter of historical
legacy that they didn't.

-- 
greg


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

В списке pgsql-bugs по дате отправления:

Предыдущее
От: hvisage@gmail.com
Дата:
Сообщение: [BUGS] BUG #14827: "ALTER TABLE... IF NOT EXISTS...ADD.. BIGSERIAL" leavesextra sequences
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [BUGS] BUG #14825: enum type: unsafe use?