Re: bgwriter, regression tests, and default shared_buffers settings - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: bgwriter, regression tests, and default shared_buffers settings
Date
Msg-id 50072ADB.3010105@dunslane.net
Whole thread Raw
In response to bgwriter, regression tests, and default shared_buffers settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bgwriter, regression tests, and default shared_buffers settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: bgwriter, regression tests, and default shared_buffers settings  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 07/18/2012 03:59 PM, Tom Lane wrote:
> 2. It's rather disturbing that a fairly large swath of functionality
> just stopped getting tested at all by the buildfarm.  Do we want to
> rethink the shared_buffers increase?  Or artificially bloat the
> regression database to make it larger than 128MB?  Or do something else
> to ensure we still exercise the DB-bigger-than-buffers case?

A couple of other ideas:

The buildfarm does have the ability to set config data after initdb has 
run (which I just enhanced in the latest release). So a buildfarm owner 
could add a config line for shared_buffers which would override what 
initdb had set.

Or we could provide an initdb flag which would set an upper bound on 
shared_buffers, and have make check (at least) use it.

I'd rather not bloat the regression database if we can reasonably avoid 
it. Buildfarm members are often tight on space.

cheers

andrew






pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PERFORM] DELETE vs TRUNCATE explanation
Next
From: Tom Lane
Date:
Subject: Re: row literal problem