Re: Planner selects different execution plans depending on limit

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Planner selects different execution plans depending on limit
Дата
Msg-id 16905.1347557599@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Planner selects different execution plans depending on limit  (Bill Martin <bill.martin@communote.com>)
Ответы Re: Planner selects different execution plans depending on limit
Список pgsql-performance
Bill Martin <bill.martin@communote.com> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> He can do it without having to change his schema --- but it's the index
>> column, not the underlying content column, that needs its statistics
>> target adjusted.

> How can I adjust the statistics target of the index?

Just pretend it's a table.

    ALTER TABLE index_name ALTER COLUMN column_name SET STATISTICS ...

You'll need to look at the index (eg with \d) to see what the name of
the desired column is, since index expressions have system-assigned
column names.

            regards, tom lane


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

Предыдущее
От: Bill Martin
Дата:
Сообщение: Re: Planner selects different execution plans depending on limit
Следующее
От: Ross Reedstrom
Дата:
Сообщение: AppScale backend datastore (NoSQL again kind of)