Re: bgwriter, regression tests, and default shared_buffers settings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: bgwriter, regression tests, and default shared_buffers settings
Date: 2012-07-19 14:12:19
Message-ID: 20470.1342707139@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jul 18, 2012 at 5:30 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> Or we could provide an initdb flag which would set an upper bound on
>> shared_buffers, and have make check (at least) use it.

> How about a flag that sets the exact value for shared_buffers, rather
> than a maximum? I think a lot of users would like initdb
> --shared-buffers=8GB or whatever.

That would be significantly harder to deploy in the buildfarm context.
We don't know that all the animals are capable of coping with 16MB
(or whatever target we settle on for make check) today.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-07-19 14:32:00 Re: bgwriter, regression tests, and default shared_buffers settings
Previous Message Tom Lane 2012-07-19 14:09:26 Re: [PERFORM] DELETE vs TRUNCATE explanation