Re: Failures with installcheck and low work_mem value in 13~ - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Failures with installcheck and low work_mem value in 13~
Date
Msg-id CAH2-Wznd6YmiLo7kx1_RcraW0-PMzm0EBUa+hFECKAvyL22m8A@mail.gmail.com
Whole thread Raw
In response to Re: Failures with installcheck and low work_mem value in 13~  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Failures with installcheck and low work_mem value in 13~
List pgsql-hackers
On Fri, Jun 19, 2020 at 10:27 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> > I don't think the tests can be made not to depend on work_mem, because
> > it costing of sort / incremental sort depends on the value. I agree
> > setting the work_mem at the beginning of the test script is the right
> > solution.
>
> I'm a bit skeptical about changing anything here.  There are quite
> a large number of GUCs that can affect the regression results, and
> it wouldn't be sane to try to force them all to fixed values.  For
> one thing, that'd be a PITA to maintain, and for another, it's not
> infrequently useful to run the tests with nonstandard settings to
> see what happens.

+1

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Failures with installcheck and low work_mem value in 13~
Next
From: Tomas Vondra
Date:
Subject: Re: compile cube extension with float4 precision storing