On 07/18/2012 05:37 PM, Tom Lane wrote:
Andrew Dunstan <and...@dunslane.net> writes:
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.
Agreed on not wanting to bloat the regression DB just for this reason.
We see enough "out of disk space" failures already in the buildfarm.
I like the idea of modifying make check only, because then a typical
buildfarm run could exercise both DB-smaller-than-buffers (in the
installcheck case) and DB-larger-than-buffers (in make check).
Agreed. Something like:
--max_shared_buffers=32MB
for initdb, plus code to use it in pg_regress, should fit the bill.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
