Re: plan with result cache is very slow when work_mem is not enough

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: plan with result cache is very slow when work_mem is not enough
Date: 2021-05-08 12:07:37
Message-ID: 021a54d6-5603-d830-263b-6fc88fa0ac7b@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 5/8/21 1:27 PM, David Rowley wrote:
> On Sat, 8 May 2021 at 22:33, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>> I don't know if there's a better way to do these tests, but if there's
>> not I'd not worry about it too much for now.
>
> So you're -1 on the proposed patch?
>

Oh! I have not noticed there was a patch. No, I'm not against the patch,
if it improves the testing (and you're right it's better to do some
testing even without evictions).

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-05-08 13:13:09 Re: Small issues with CREATE TABLE COMPRESSION
Previous Message David Rowley 2021-05-08 11:27:04 Re: plan with result cache is very slow when work_mem is not enough