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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(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 11:27:04
Message-ID: CAApHDvpkZWnao6j-MeszfBzb6w7AiADbo1i=jYYY-6TEjX2kww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-05-08 12:07:37 Re: plan with result cache is very slow when work_mem is not enough
Previous Message Tomas Vondra 2021-05-08 10:33:41 Re: plan with result cache is very slow when work_mem is not enough