All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Eisentraut <peter_e@gmx.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
	Nadia Derbey <Nadia.Derbey@bull.net>,
	Solofo Ramangalahy <Solofo.Ramangalahy@bull.net>,
	Manfred Spraul <manfred@colorfullife.com>,
	Pierre Peiffer <peifferp@gmail.com>,
	containers@lists.osdl.org
Subject: Re: [Bugme-new] [Bug 11381] New: default shmmax
Date: Thu, 21 Aug 2008 11:08:43 +0300	[thread overview]
Message-ID: <200808211108.46443.peter_e@gmx.net> (raw)
In-Reply-To: <20080820195509.00994d51@lxorguk.ukuu.org.uk>

Alan Cox wrote:
> > It would be useful to get distro input on this.  Do they override the
> > kernel default at boot time?  If so, what do they do?
>
> Red Hat provide a sysctl tuning config file and I believe things like the
> Oracle install docs cover this.
>
> There is btw no earthly reason why a postgres package can't include a
> tool to do this or postgres can't check and update it as part of its
> own set up and config file options

I have explored this, it would be possible, but it would be a pain in the 
neck.  You'd need to add an option to postgres to print out how much shared 
memory you would need for a given configuration (because there are multiple 
factors in this), run this across all postgres instances on the machine, sum 
it up, then arrange for this to be fed back to sysctl or pasted back into 
sysctl.conf, being careful not to override or lower an existing setting that 
might have wanted to reserve space for other things.  Note that to make this 
robust you would have to rerun this after every configuration change + 
restart cycle across all postgres instances on the machine, race conditions 
included.  And you'd probably violate a few packaging guidelines on the way.  
Plus, this would have to be distro-specific (not Linux-specific, but 
distro-specific), doesn't help managed hosting with no root access, and 
doesn't help people building from source.  So altogether it is very 
complicated.

In the meantime I am trying to explore why the shmmax default is what it is.  
Or why it has to exist at all.  If we can figure that out, maybe we can solve 
a lot of users a lot of trouble with much less effort (including Oracle 
users, why not).

  reply	other threads:[~2008-08-21  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11381-10286@http.bugzilla.kernel.org/>
2008-08-20 19:00 ` [Bugme-new] [Bug 11381] New: default shmmax Andrew Morton
2008-08-20 18:55   ` Alan Cox
2008-08-21  8:08     ` Peter Eisentraut [this message]
2008-08-20 19:12   ` adobriyan
2008-08-20 19:16     ` adobriyan
     [not found]   ` <20080820120043.e6e7e436.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-08-21  7:58     ` Solofo.Ramangalahy-6ktuUTfB/bM
2008-08-21  8:24       ` Peter Eisentraut
2008-08-21  8:19   ` Peter Eisentraut

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200808211108.46443.peter_e@gmx.net \
    --to=peter_e@gmx.net \
    --cc=Nadia.Derbey@bull.net \
    --cc=Solofo.Ramangalahy@bull.net \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=containers@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=peifferp@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.