| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Subject: | Re: Failures with installcheck and low work_mem value in 13~ |
| Date: | 2020-06-19 17:28:56 |
| Message-ID: | CAH2-Wznd6YmiLo7kx1_RcraW0-PMzm0EBUa+hFECKAvyL22m8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 19, 2020 at 10:27 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-06-19 17:30:30 | Re: compile cube extension with float4 precision storing |
| Previous Message | Tom Lane | 2020-06-19 17:27:09 | Re: Failures with installcheck and low work_mem value in 13~ |