Re: Difference in execution plans pg12 vs pg14
| От | Imre Samu |
|---|---|
| Тема | Re: Difference in execution plans pg12 vs pg14 |
| Дата | |
| Msg-id | CAJnEWwm75o=hd2VUCiQDL6n+N0PuCG3zqV_8EZu4A_FZ5k-LvA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Difference in execution plans pg12 vs pg14 (Дмитрий Иванов <firstdismay@gmail.com>) |
| Ответы |
Re: Difference in execution plans pg12 vs pg14
|
| Список | pgsql-general |
Hi Dmitry,
pg12:
> Execution Time: 44.123 ms
pg14:
> JIT:
> Functions: 167
> Options: Inlining true, Optimization true, Expressions true, Deforming true
> Timing: Generation 9.468 ms, Inlining 55.237 ms, Optimization 507.548 ms, Emission 347.932 ms, Total 920.185 ms
> Execution Time: 963.258 ms
> Functions: 167
> Options: Inlining true, Optimization true, Expressions true, Deforming true
> Timing: Generation 9.468 ms, Inlining 55.237 ms, Optimization 507.548 ms, Emission 347.932 ms, Total 920.185 ms
> Execution Time: 963.258 ms
please check the JIT settings ;
and test with: jit = off;
regards,
Imre
Дмитрий Иванов <firstdismay@gmail.com> ezt írta (időpont: 2021. dec. 11., Szo, 2:01):
Afternoon. I was able to make the necessary changes to my base needed to migrate win_pg12 to debian pg14.
But there is a new problem, which was not there at the initial stage so I checked:
win_pg12:
-> Index Scan using index_class_tree_full on class c (cost=0.28..2.50 rows=1 width=235) (actual time=0.030..0.032 rows=1 loops=1)
Index Cond: (id = 650)
debian_pg14:
-> Index Scan using index_class_tree_full on class c (cost=0.28..2.50 rows=1 width=235) (actual time=842.795..842.796 rows=1 loops=1)
Index Cond: (id = 650)
I'm wondering where to dig next...--Best regards, Dmitry!
В списке pgsql-general по дате отправления: