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 CAApHDvq6=LW5DLk-4iD0zM5zrfSNqWBg_3Ch-_UKFEvfmKv1XQ@mail.gmail.com
Whole thread Raw
In response to Re: plan with result cache is very slow when work_mem is not enough  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List pgsql-hackers
On Sun, 9 May 2021 at 00:07, Tomas Vondra <tomas.vondra@enterprisedb.com> wrote:
>
>
> On 5/8/21 1:27 PM, David Rowley wrote:
> > On Sat, 8 May 2021 at 22:33, Tomas Vondra <tomas.vondra@enterprisedb.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).

There seems to be plenty of other ideas floating around, but since
nobody seems to be objecting to reducing the Assert overheads, I've
pushed the proposed patch.

The more I thought about this, the more I think I should have done it
this way in the first place.

David



pgsql-hackers by date:

Previous
From: Peter Lee
Date:
Subject: Re: Will Postgres12 installed on a RHEL 6 server continue to function after the server get O/S upgrade to RHEL 7?
Next
From: Zhihong Yu
Date:
Subject: Re: SQL/JSON: functions