On Sat, 3 Apr 2021 at 09:47, Andres Freund wrote:
> Since this commit I am seeing
>
> In file included from /home/andres/src/postgresql/src/include/postgres.h:46,
> from
> /home/andres/src/postgresql/src/backend/executor/nodeResultCache.c:67:
> /home/andres/src/postgresql/src/bac
Hi,
On 2021-04-02 01:11:35 +, David Rowley wrote:
> Add Result Cache executor node (take 2)
Since this commit I am seeing
In file included from /home/andres/src/postgresql/src/include/postgres.h:46,
from
/home/andres/src/postgresql/src/backend/executor/nodeResultCache.c:67:
Add Result Cache executor node (take 2)
Here we add a new executor node type named "Result Cache". The planner
can include this node type in the plan to have the executor cache the
results from the inner side of parameterized nested loop joins. This
allows caching of tuples for sets of parameter
On Thu, 1 Apr 2021 at 14:36, Tom Lane wrote:
>
> Tomas Vondra writes:
> > On 4/1/21 2:52 AM, Tom Lane wrote:
> >> Anyway, it looks like I can probably reproduce it on florican's
> >> host, if you still need help understanding it tomorrow. But
> >> I remain really dubious that this can work at al
Tomas Vondra writes:
> On 4/1/21 2:52 AM, Tom Lane wrote:
>> Anyway, it looks like I can probably reproduce it on florican's
>> host, if you still need help understanding it tomorrow. But
>> I remain really dubious that this can work at all. Question:
>> have you tried that test under CLOBBER_CA
On 4/1/21 2:52 AM, Tom Lane wrote:
> David Rowley writes:
>> On Thu, 1 Apr 2021 at 12:32, David Rowley wrote:
>>> Add Result Cache executor node
>
>> I'm not really sure why yet why many buildfarm members don't like this.
>
> Something that struck me is that the animals that stayed green wer
David Rowley writes:
> On Thu, 1 Apr 2021 at 12:32, David Rowley wrote:
>> Add Result Cache executor node
> I'm not really sure why yet why many buildfarm members don't like this.
Something that struck me is that the animals that stayed green were
almost exclusively Debian and macOS, while the
On Thu, 1 Apr 2021 at 12:32, David Rowley wrote:
> Add Result Cache executor node
I'm not really sure why yet why many buildfarm members don't like this.
You can see below that the Index scan was executed 20 times (loops=20)
-> Result Cache (actual rows=1 loops=1000)
On Thu, 1 Apr 2021 at 12:47, Tom Lane wrote:
>
> David Rowley writes:
> > Add Result Cache executor node
>
> You didn't seriously believe that EXPLAIN ANALYZE numbers
> would be stable in the buildfarm, did you?
If you look a bit harder you can probably see which ones I thought
would be stable a
David Rowley writes:
> Add Result Cache executor node
You didn't seriously believe that EXPLAIN ANALYZE numbers
would be stable in the buildfarm, did you?
regards, tom lane
Add Result Cache executor node
Here we add a new executor node type named "Result Cache". The planner
can include this node type in the plan to have the executor cache the
results from the inner side of parameterized nested loop joins. This
allows caching of tuples for sets of parameters so that
11 matches
Mail list logo
