pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: Greg Copeland <greg@CopelandConsulting.Net>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>
Subject: Re: Changing the default configuration (was Re:
Date: Tue, 11 Feb 2003 23:24:26 -0500
Message-ID: <495.1045023866@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.33.0302111300160.29989-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0302111300160.29989-100000@css120.ihs.com>

"scott.marlowe" <scott.marlowe@ihs.com> writes:
> ... The original choice of 32 was set because the original 
> choice of 64 shared memory blocks as the most we could hope for on common 
> OS installs.  Now that we're looking at cranking that up to 1000, 
> shouldn't max connections get a look too?

Actually I think max-connections at 32 was set because of SEMMAX limits,
and had only the most marginal connection to shared_buffers (anyone care
to troll the archives to check?)  But sure, let's take another look at
the realistic limits today.

> ... If he starts running out of semaphores, that's a 
> problem he can address while his database is still up and running in most 
> operating systems, at least in the ones I use.

Back in the day, this took a kernel rebuild and system reboot to fix.
If this has changed, great ... but on exactly which Unixen can you
alter SEMMAX on the fly?

> So, my main point is that any setting that requires you to shut down 
> postgresql to make the change, we should pick a compromise value that 
> means you never likely will have to shut down the database once you've 
> started it up and it's under load.

When I started using Postgres, it did not allocate the max number of
semas it might need at startup, but was instead prone to fail when you
tried to open the 17th or 33rd or so connection.  It was universally
agreed to be an improvement to refuse to start at all if we could not
meet the specified max_connections setting.  I don't want to backtrack
from that.  If we can up the default max_connections setting, great ...
but let's not increase the odds of failing under load.

			regards, tom lane



view thread (65+ messages)  latest in thread

Message-ID: <495.1045023866@sss.pgh.pa.us>
Permalink:  ../495.1045023866@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/495.1045023866@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, scott.marlowe@ihs.com, greg@CopelandConsulting.Net, pgsql-hackers@postgresql.org
  Subject: Re: Changing the default configuration (was Re:
  In-Reply-To: <495.1045023866@sss.pgh.pa.us>
  References: <Pine.LNX.4.33.0302111300160.29989-100000@css120.ihs.com> <495.1045023866@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