Re: Proof-of-concept for initdb-time shared_buffers selection

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Manfred Koizar <mkoi-pg(at)aon(dot)at>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Proof-of-concept for initdb-time shared_buffers selection
Date: 2003-07-31 16:43:32
Message-ID: 200307310943.32232.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Manfred,

> Can't this be done on postmaster startup? I think of two GUC
> variables where there is only one today: min_shared_buffers and
> max_shared_buffers. If allocation for the max_ values fails, the
> numbers are decreased in a loop of, say, 10 steps until allocation
> succeeds, or even fails at the min_ values.

I think the archives are back up. Take a look at this thread; we already had
this discussion at some length, and decided that a max of 1000 was reasonable
in advance of user tuning. And, I believe, Tom has already written the code.

--
Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2003-07-31 16:48:18 Re: followup on previous
Previous Message Tom Lane 2003-07-31 15:31:26 Re: Error messages --- now that we've got it, do you like

Browse pgsql-patches by date

  From Date Subject
Next Message Joe Conway 2003-07-31 17:56:43 preload libraries patch [was: [GENERAL] hexadecimal to decimal]
Previous Message Andreas Pflug 2003-07-31 16:05:27 Re: [Fwd: Re: ruleutils with pretty-print option]