Re: bad JIT decision
От
Scott Ribe
Тема
Re: bad JIT decision
Дата
Msg-id
559519F3-5285-4F2B-A88F-0067382761A7@elevated-dev.com
Ответ на
Re: bad JIT decision (David Rowley)
Список
Дерево обсуждения
bad JIT decision Scott Ribe <scott_ribe@elevated-dev.com>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision Scott Ribe <scott_ribe@elevated-dev.com>
Re: bad JIT decision "Andres Freund" <andres@anarazel.de>
Re: bad JIT decision Tom Lane <tgl@sss.pgh.pa.us>
Re: bad JIT decision Andres Freund <andres@anarazel.de>
Re: bad JIT decision Alvaro Herrera <alvherre@2ndquadrant.com>
Re: bad JIT decision Scott Ribe <scott_ribe@elevated-dev.com>
Re: bad JIT decision Alvaro Herrera <alvherre@2ndquadrant.com>
Re: bad JIT decision Andres Freund <andres@anarazel.de>
Re: bad JIT decision Tom Lane <tgl@sss.pgh.pa.us>
Re: bad JIT decision Tom Lane <tgl@sss.pgh.pa.us>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision Scott Ribe <scott_ribe@elevated-dev.com>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision Tom Lane <tgl@sss.pgh.pa.us>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision Tom Lane <tgl@sss.pgh.pa.us>
Re: bad JIT decision Andres Freund <andres@anarazel.de>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision Andres Freund <andres@anarazel.de>
Re: bad JIT decision Andres Freund <andres@anarazel.de>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
Re: bad JIT decision David Rowley <dgrowleyml@gmail.com>
> On Jul 24, 2020, at 4:26 PM, David Rowley wrote: > > It does not really take into account the cost of jitting. That is what I was missing. I read about JIT when 12 was pre-release; in re-reading after my post I see that it does not attempt to estimate JIT cost. And in thinking about it, I realize that would be next to impossible to anticipate how expensive LLVM optimizstion was going to be. In the case where a set of functions is replicated across partitions, it would be possible to do them once, then project the cost of the copies. Perhaps for PG 14 as better support for the combination of JIT optimization and highly-partitioned data ;-)
В списке pgsql-general по дате отправления