pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>
Cc: pgsql-advocacy@postgresql.org
Subject: Re: [HACKERS] Changing the default configuration (was Re:
Date: Wed, 12 Feb 2003 00:27:31 -0500
Message-ID: <932.1045027651@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.44.0302112211150.7753-100000@peter.localdomain>
References: <Pine.LNX.4.44.0302112211150.7753-100000@peter.localdomain>

Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> We could retarget to try to stay under SHMMAX=4M, which I think is
>> the next boundary that's significant in terms of real-world platforms
>> (isn't that the default SHMMAX on some BSDen?).  That would allow us
>> 350 or so shared_buffers, which is better, but still not really a
>> serious choice for production work.

> What is a serious choice for production work?

Well, as I commented later in that mail, I feel that 1000 buffers is
a reasonable choice --- but I have to admit that I have no hard data
to back up that feeling.  Perhaps we should take this to the
pgsql-perform list and argue about reasonable choices.

A separate line of investigation is "what is the lowest common
denominator nowadays?"  I think we've established that SHMMAX=1M
is obsolete, but what replaces it as the next LCD?  4M seems to be
correct for some BSD flavors, and I can confirm that that's the
current default for Mac OS X --- any other comments?

			regards, tom lane



view thread (65+ messages)  latest in thread

Message-ID: <932.1045027651@sss.pgh.pa.us>
Permalink:  ../932.1045027651@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/932.1045027651@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, peter_e@gmx.net, merlin.moncure@rcsonline.com, pgsql-hackers@postgresql.org, pgsql-advocacy@postgresql.org
  Subject: Re: [HACKERS] Changing the default configuration (was Re:
  In-Reply-To: <932.1045027651@sss.pgh.pa.us>
  References: <Pine.LNX.4.44.0302112211150.7753-100000@peter.localdomain> <932.1045027651@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