Re: bad estimates / non-scanning aggregates

Поиск
Список
Период
Сортировка
От Bruno Wolff III
Тема Re: bad estimates / non-scanning aggregates
Дата
Msg-id 20030829033818.GA5577@wolff.to
обсуждение исходный текст
Ответ на Re: bad estimates / non-scanning aggregates  (Ken Geis <kgeis@speakeasy.org>)
Ответы Re: bad estimates  (Ken Geis <kgeis@speakeasy.org>)
Список pgsql-performance
On Thu, Aug 28, 2003 at 20:00:32 -0700,
  Ken Geis <kgeis@speakeasy.org> wrote:
> Bruno Wolff III wrote:
> >>Not according to the optimizer!  Plus, this is not guaranteed to return
> >>the correct results.
> >
> >For it to be fast you need an index on (stock_id, price_date) so that
> >you can use an index scan.
>
> I already said that such an index existed.  In fact, it is the primary
> key of the table.  And yes, I *am* analyzed!

Your original example didn't actually match that of the table you are showing
examples from. In that example the second half of the primary key was the
date not the end of the day price. If this is the case for the real table,
then that is the reason the distinct on doesn't help.

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

Предыдущее
От: Ken Geis
Дата:
Сообщение: Re: bad estimates / non-scanning aggregates
Следующее
От: Eko Pranoto
Дата:
Сообщение: PostgreSQL HDD Grow capacity