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

From Tom Lane
Subject Re: plan with result cache is very slow when work_mem is not enough
Date
Msg-id 242172.1620494497@sss.pgh.pa.us
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>)
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> so 8. 5. 2021 v 9:39 odesílatel David Rowley <dgrowleyml@gmail.com> napsal:
>> So, I'm -1 for "heavy asserts".

> Personally, I have not problem with too slow assertions, although it is not
> too practical.

I'm very much on David's side here.  I'm currently trying to figure out
why CLOBBER_CACHE_ALWAYS tests have gotten something like 10% slower
in the past six weeks or so --- if you look at hyrax for example,
it finished "make check" in 12:52:44 in its last fully-green run
back in mid-March, while the latest report shows 14:08:18.  I think
something needs to be done about that.  It's bad enough that no
developers will run cache-clobber tests by hand; but if it takes
a week to get buildfarm feedback, you've got exactly the same
problems David describes.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Identify LWLocks in tracepoints
Next
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON: functions