RE: [HACKERS] postmaster failure with 2-23 snapshot

Here is what I added to my /etc/system on Solaris 7:

set shmsys:shminfo_shmmax=16777216
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=128
set shmsys:shminfo_shmseg=51
*
set semsys:seminfo_semmap=128
set semsys:seminfo_semmni=128
set semsys:seminfo_semmns=8192
set semsys:seminfo_semmnu=8192
set semsys:seminfo_semmsl=64
set semsys:seminfo_semopm=32
set semsys:seminfo_semume=32

Of course, this is way more than you need to run 64 backends, this
will accommodate thousands of semaphores, but not much more than 128
backends due to the shared memory needs... You might want to run a
sysdef to see the defaults first and then pick your tunables.

DwD

> -----Original Message-----
> From: owner-pgsql-hackers(at)postgreSQL(dot)org
> [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Tom Lane
> Sent: Tuesday, February 23, 1999 7:04 PM
> To: Brian P Millett
> Cc: pgsql-hackers
> Subject: Re: [HACKERS] postmaster failure with 2-23 snapshot
>
>
> > vlad: postmaster -i
> > IpcMemoryCreate: shmget failed (Invalid argument) key=5432001,
> > size=1137426, permission=600
>
> I think shmget returns that error code when the requested size is
> larger than the system limit on shared memory block size. Check
> your kernel parameters (SHMMAX and friends).
>
> You might find that starting the postmaster with a smaller value
> of -N is an easier answer than reconfiguring your kernel.
>
> regards, tom lane
>