Manfred Koizar <mkoi-pg(at)aon(dot)at> writes:
> On Fri, 04 Jul 2003 15:29:37 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>> The attached patch shows how initdb can dynamically determine reasonable
>> shared_buffers and max_connections settings that will work on the
>> current machine.
> Can't this be done on postmaster startup?
Why would that be a good idea? Seems to me it just offers a fresh
opportunity to do the wrong thing at every startup. We'v had troubles
enough with problems that appear only when the postmaster is started by
hand rather than by boot script, or vice versa; this would just add
another unknown to the equation.
> This would make the lives easier for the folks trying to come up with
> default .conf files, e.g.
> min_shared_buffers = 64
> max_shared_buffers = 2000
> could cover a fairly large range of low level to mid level machines.
Not unless their notion of a default .conf file includes a preinstalled
$PGDATA directory. Under ordinary circumstances, initdb will get run
locally on the target machine, and should come up with a valid value.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2003-07-31 13:58:31|
|Subject: Re: version mismatch message |
|Previous:||From: Andreas Pflug||Date: 2003-07-31 12:39:21|
|Subject: Re: followup on previous|
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2003-07-31 14:05:25|
|Subject: Re: Check for failed memory allocations in libpq |
|Previous:||From: Tom Lane||Date: 2003-07-31 13:37:44|
|Subject: Re: [Fwd: Re: ruleutils with pretty-print option] |