Re: pg16: XX000: could not find pathkey item to sort
От | David Rowley |
---|---|
Тема | Re: pg16: XX000: could not find pathkey item to sort |
Дата | |
Msg-id | CAApHDvqira92LLPbW37azL+fDEm7yvWni89YekB9G751W7nEBw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg16: XX000: could not find pathkey item to sort (David Rowley <dgrowleyml@gmail.com>) |
Ответы |
Re: pg16: XX000: could not find pathkey item to sort
Re: pg16: XX000: could not find pathkey item to sort |
Список | pgsql-hackers |
On Mon, 9 Oct 2023 at 12:42, David Rowley <dgrowleyml@gmail.com> wrote: > Maybe it's worth checking the total planning time spent in a run of > the regression tests with and without the patch to see how much > overhead it adds to the "average case". I've now pushed the patch that trims off the Pathkeys for the ORDER BY / DISTINCT aggregates. As for the patch to verify the pathkeys during create plan, I patched master with the attached plan_times.patch.txt and used the following to check the time spent in the planner for 3 runs of make installcheck. $ for i in {1..3}; do pg_ctl start -D pgdata -l plantime.log > /dev/null && cd pg_src && make installcheck > /dev/null && cd .. && grep "planning time in" plantime.log|sed -E -e 's/.*planning time in (.*) nanoseconds/\1/'|awk '{nanoseconds += $1} END{print nanoseconds}' && pg_ctl stop -D pgdata > /dev/null && rm plantime.log; done Master: 1855788104 1839655412 1740769066 Patched: 1917797221 1766606115 1881322655 Those results are a bit noisy. Perhaps a few more runs might yield more consistency, but it seems that there's not too much overhead to it. If I take the minimum value out of the 3 runs from each, it comes to about 1.5% extra time spent in planning. Perhaps that's OK. David
Вложения
В списке pgsql-hackers по дате отправления: