Re: plan with result cache is very slow when work_mem is not enough
От | David Rowley |
---|---|
Тема | Re: plan with result cache is very slow when work_mem is not enough |
Дата | |
Msg-id | CAApHDvrJvhj2E9taBH13Nr1eVDyg1A9UuXz1xeWQDaLagWsTTg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: plan with result cache is very slow when work_mem is not enough (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: plan with result cache is very slow when work_mem is not enough
Re: plan with result cache is very slow when work_mem is not enough |
Список | pgsql-hackers |
On Sun, 9 May 2021 at 03:29, Pavel Stehule <pavel.stehule@gmail.com> wrote: > Personally, I have not problem with too slow assertions, although it is not too practical. The main problem is some shock,and feeling so some is wrong. I spent 1 hour detecting if it is a bug or not. Thanks for spending the time figuring out where the slowness came from. > Can it be possible to identify this situation? > > Maybe use some specific name of this routine - like > > assert_only_check_xxxx > > Then I can see this warning in perf, and I don't need to do other or deeper checks I don't think we need to go around leaving clues for people who run perf on cassert builds. I think anyone doing that should just never expect any meaningful results. David
В списке pgsql-hackers по дате отправления: