Re: [HACKERS] Changing the default configuration (was Re:

scott.marlowe <scott.marlowe@ihs.com>

From: "scott.marlowe" <scott.marlowe@ihs.com>
To: Curt Sampson <cjs@cynic.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Merlin Moncure <merlin.moncure@rcsonline.com>, PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>, <pgsql-advocacy@postgresql.org>
Date: 2003-02-12T01:02:09Z
Lists: pgsql-hackers, pgsql-performance
On Wed, 12 Feb 2003, Curt Sampson wrote:

> On Tue, 11 Feb 2003, Tom Lane wrote:
> 
> > It's a lot too conservative.  I've been thinking for awhile that we
> > should adjust the defaults.
> 
> Some of these issues could be made to Just Go Away with some code
> changes. For example, using mmap rather than SysV shared memory
> would automatically optimize your memory usage, and get rid of the
> double-buffering problem as well. If we could find a way to avoid using
> semephores proportional to the number of connections we have, then you
> wouldn't have to worry about that configuration parameter, either.
> 
> In fact, some of this stuff might well improve our portability, too.
> For example, mmap is a POSIX standard, whereas shmget is only an X/Open
> standard. That makes me suspect that mmap is more widely available on
> non-Unix platforms. (But I could be wrong.)

I'll vote for mmap.  I use the mm libs with apache/openldap/authldap and 
it is very fast and pretty common nowadays.  It seems quite stable as 
well.