Re: plan with result cache is very slow when work_mem is not enough - Mailing list pgsql-hackers

From David Rowley
Subject Re: plan with result cache is very slow when work_mem is not enough
Date
Msg-id CAApHDvrJvhj2E9taBH13Nr1eVDyg1A9UuXz1xeWQDaLagWsTTg@mail.gmail.com
Whole thread Raw
In response to Re: plan with result cache is very slow when work_mem is not enough  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses 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
List 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 by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: SQL/JSON: functions
Next
From: Alexander Korotkov
Date:
Subject: Re: JSON doc example (matchiness)