Re: Unwanted expression simplification in PG12b2

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Unwanted expression simplification in PG12b2
Дата
Msg-id CA+TgmoYrwqrMjMWf8CFNQZoLvd0+EmR5ZYba775H4yPOJz+xFw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Unwanted expression simplification in PG12b2  (Darafei "Komяpa" Praliaskouski <me@komzpa.net>)
Ответы Re: Unwanted expression simplification in PG12b2  ("Finnerty, Jim" <jfinnert@amazon.com>)
Список pgsql-hackers
On Sun, Sep 22, 2019 at 7:47 AM Darafei "Komяpa" Praliaskouski
<me@komzpa.net> wrote:
> A heuristic I believe should help my case (and I hardly imagine how it can break others) is that in presence of
Gather,all the function calls that are parallel safe should be pushed into it. 

The cost of pushing data through the Sort is not necessarily
insignificant.  Your functions are (IIUC) extremely expensive, so it's
worth going to any length to reduce the time spent evaluating them.
However, if someone has ||(text,text) in the tlist, that might be the
wrong approach, because it's not saving much to compute that earlier
and it might make the sort a lot wider, especially if de-TOASTing is
involved.

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



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

Предыдущее
От: Andrew Gierth
Дата:
Сообщение: Re: Efficient output for integer types
Следующее
От: Binguo Bao
Дата:
Сообщение: Re: [proposal] de-TOAST'ing using a iterator