pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Sean Chittenden <sean@chittenden.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Moving postgresql.conf tunables into 2003...
Date: Fri, 04 Jul 2003 13:15:17 -0400
Message-ID: <27905.1057338917@sss.pgh.pa.us> (raw)
In-Reply-To: <200307031938.15357.josh@agliodbs.com>
References: <20030703190502.GR72567@perrin.int.nxad.com>
	<200307031938.15357.josh@agliodbs.com>

Josh Berkus <josh@agliodbs.com> writes:
> Tom Comments:
>> I was arguing awhile back for bumping the default shared_buffers up,
>> but the discussion trailed off with no real resolution.

> I think we ran up against the still far-too-low SHMMAX settings in most 
> *nixes.   We could raise this default once we can supply a script which will 
> help the user bump up the OS's memory settings at, say, initDB time.

Actually, I think it would not be hard to get initdb to test whether
larger shared-memory settings would work.  We could do something like
try -B of 64, 256, 512, 1024, and insert into postgresql.conf the
largest value that works.  I would want it to top out at a few thousand
at most, because I don't think a default installation should try to
commandeer the whole machine, but if we could get the typical
installation to be running with even 1000 buffers rather than 64,
we'd be *way* better off.  (See "Postgres vs MySQL" thread nearby.)

We could possibly also have initdb print some kind of message if it's
forced to use an unreasonably small value for shared_buffers, so that
people might have a clue that they need to do kernel reconfiguration.

Comments?

			regards, tom lane



view thread (45+ messages)  latest in thread

Message-ID: <27905.1057338917@sss.pgh.pa.us>
Permalink:  ../27905.1057338917@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27905.1057338917@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, sean@chittenden.org
  Subject: Re: Moving postgresql.conf tunables into 2003...
  In-Reply-To: <27905.1057338917@sss.pgh.pa.us>
  References: <20030703190502.GR72567@perrin.int.nxad.com> <200307031938.15357.josh@agliodbs.com> <27905.1057338917@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox