Re: Parallel append plan instability/randomness

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Parallel append plan instability/randomness
Дата
Msg-id CA+TgmobaRGXb0tNZCTn82PaLcssXzEg++yQGS4OY2Ri9Ypty_g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Parallel append plan instability/randomness  (Jim Finnerty <jfinnert@amazon.com>)
Ответы Re: Parallel append plan instability/randomness
Список pgsql-hackers
On Mon, Jan 8, 2018 at 11:28 AM, Jim Finnerty <jfinnert@amazon.com> wrote:
> Ordering the plan output elements by estimated cost will cause spurious plan
> changes to be reported after table cardinalities change.  Can we choose an
> explain output order that is stable to changes in cardinality, please?

No.  The order of the plans in the EXPLAIN output isn't some kind of
display artifact.  Parallel Append sorts the paths by cost and by
whether they are partial, for reasons explained in the comments in
create_append_path(), and EXPLAIN prints them in that order.

In general, if you expect to be able to change the contents of the
tables in the regression test database without changing the results of
the regression test queries, you are in for a lot of disappointment.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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

Предыдущее
От: Jim Finnerty
Дата:
Сообщение: Re: Parallel append plan instability/randomness
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Parallel append plan instability/randomness