Re: Difference in execution plans pg12 vs pg14

2021-12-11 Thread Дмитрий Иванов
Thanks to Imre Samu's help, I found out that this is an unwarranted interference of the JIT compilation. When it is disabled, the short queries work stably. Before the problem started, I purposely increased the amount of surrogate data to evaluate performance. Perhaps the logic for enabling JIT com

Re: Difference in execution plans pg12 vs pg14

2021-12-11 Thread Peter J. Holzer
On 2021-12-11 06:00:40 +0500, Дмитрий Иванов wrote: > 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_

Re: Difference in execution plans pg12 vs pg14

2021-12-11 Thread Дмитрий Иванов
Ok, I will check. Now I have even more questions. This behavior appeared, it was not there in the first place. jit-compilation down my long aggregation queries by about half on average. How do I adjust this correctly? #jit_provider = 'llvmjit' # JIT library to use #jit_above_cost = 10 # perfor

Re: Difference in execution plans pg12 vs pg14

2021-12-10 Thread Imre Samu
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.25

Re: Difference in execution plans pg12 vs pg14

2021-12-10 Thread Дмитрий Иванов
Yes, I did. Step1 sudo /usr/lib/postgresql/14/bin/pg_dump --file "/home/dismay/uchet/Uchet.backup" --host "server" --port "5999" --username "back" --no-password --verbose --format=c --quote-all-identifiers --blobs --disable-triggers --encoding="UTF8" "Uchet" Step2 Manual DROP/CREATE BASE from tem

Re: Difference in execution plans pg12 vs pg14

2021-12-10 Thread Adrian Klaver
On 12/10/21 17:51, Дмитрий Иванов wrote: Yes, I did. I reset table statistics, did (VACUUM) ANALYZE, recreated index. Nothing changes. I've deleted the database many times, dozens of times. Maybe something is broken? How did you do the upgrade? -- Regards, Dmitry! сб, 11 дек. 2021 г. в 06

Re: Difference in execution plans pg12 vs pg14

2021-12-10 Thread Дмитрий Иванов
Yes, I did. I reset table statistics, did (VACUUM) ANALYZE, recreated index. Nothing changes. I've deleted the database many times, dozens of times. Maybe something is broken? -- Regards, Dmitry! сб, 11 дек. 2021 г. в 06:13, Adrian Klaver : > On 12/10/21 17:00, Дмитрий Иванов wrote: > > Afternoo

Re: Difference in execution plans pg12 vs pg14

2021-12-10 Thread Adrian Klaver
On 12/10/21 17:00, Дмитрий Иванов wrote: 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

Difference in execution plans pg12 vs pg14

2021-12-10 Thread Дмитрий Иванов
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 t