pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy]
Date: 11 Feb 2003 13:53:51 -0500
Message-ID: <1044989631.32185.151.camel@zeutrh80> (raw)
In-Reply-To: <26924.1044986473@sss.pgh.pa.us>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local>
	<26004.1044980414@sss.pgh.pa.us>
	<49391.192.168.1.12.1044985098.squirrel@mail.mayuli.com>
	<26924.1044986473@sss.pgh.pa.us>

On Tue, 2003-02-11 at 13:01, Tom Lane wrote:
> "Jon Griffin" <jon@jongriffin.com> writes:
> > So it appears that linux at least is way above your 8 meg point, unless I
> > am missing something.
> 
> Yeah, AFAIK all recent Linuxen are well above the range of parameters
> that I was suggesting (and even if they weren't, Linux is particularly
> easy to change the SHMMAX setting on).  It's other Unixoid platforms
> that are likely to have a problem.  Particularly the ones where you
> have to rebuild the kernel to change SHMMAX; people may be afraid to
> do that.

The issue as I see it is: 
Better performing vs. More Compatible Out of the box Defaults.

Perhaps a compromise (hack?):
Set the default to some default value that performs well, a value we all
agree is not too big (16M? 32M?). On startup, if the OS can't give us
what we want, instead of failing, we can try again with a smaller
amount, perhaps half the default, if that fails try again with half
until we reach some bottom threshold (1M?).

The argument against this might be: When I set shared_buffers=X, I want
X shared buffers. I don't want it to fail silently and give me less than
what I need / want.  To address this we might want to add a guc option
that controls this behavior. So we ship postgresql.conf with 32M of
shared memory and auto_shared_mem_reduction = true.  With a comment that
the administrator might want to turn this off for production.

Thoughts?  

I think this will allow most uninformed users get decent performing
defaults as most systems will accommodate this larger value.




view thread (65+ messages)  latest in thread

Message-ID: <1044989631.32185.151.camel@zeutrh80>
Permalink:  ../1044989631.32185.151.camel@zeutrh80/
Also on:    postgresql.org/message-id/1044989631.32185.151.camel@zeutrh80

 · 

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: matthew@zeut.net, tgl@sss.pgh.pa.us
  Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy]
  In-Reply-To: <1044989631.32185.151.camel@zeutrh80>
  References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <26004.1044980414@sss.pgh.pa.us> <49391.192.168.1.12.1044985098.squirrel@mail.mayuli.com> <26924.1044986473@sss.pgh.pa.us> <1044989631.32185.151.camel@zeutrh80>

* 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