Re: [PERFORM] Planner selects different execution plans depending on limit

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [PERFORM] Planner selects different execution plans depending on limit
Дата
Msg-id 28910.1347833815@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: [PERFORM] Planner selects different execution plans depending on limit  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-docs
Jeff Janes <jeff.janes@gmail.com> writes:
> On Thu, Sep 13, 2012 at 10:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> Is this documented anywhere?  I couldn't find it.  If not, which
> section would be the best one to add it to?

It's not documented, mainly because it hasn't reached the level of being
a supported feature.  I'd like to figure out how to get pg_dump to dump
such settings before we call it supported.  (The stumbling block is
exactly that index column names aren't set in stone, so it's not clear
that the ALTER command would do the right thing on dump-and-reload.)

            regards, tom lane


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

Предыдущее
От: Sebastien FLAESCH
Дата:
Сообщение: Re: Details about libpq cross-version compatibility
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [BUGS] BUG #7543: Invalid table alias: DELETE FROM table *