Re: Running some tests with different segment sizes

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Running some tests with different segment sizes
Date: 2017-09-19 18:10:28
Message-ID: 20170919181027.oayw2e6hjnrtecbq@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017-09-19 14:05:44 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I'm working on merging the customizable segment size patch [1]. I'd
> > like to run some of the regression tests using it, to guarantee
> > non-standard settings have test coverage. The reason I'd like to adapt
> > an existing test, rather than add a new run of the standard regression
> > tests, is to avoid bloating the regression time unnecessarily.
>
> Maybe there's a way to set up a buildfarm animal or two that run all
> the tests with a different segsize?

Hm, that'd work too. We could make initdb look at
getenv("PG_DEFAULT_SEGSIZE") or such? Otherwise it's probably not easy
to have all tests respect that.

I still would like to have at least one test that explicitly specifies a
different size so people can see if they outright break something, but
one would be enough if we had such an animal.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-09-19 18:24:17 Re: Re: [COMMITTERS] pgsql: Perform only one ReadControlFile() during startup.
Previous Message Tom Lane 2017-09-19 18:05:44 Re: Running some tests with different segment sizes