From: | Brian P Millett <bpm(at)ec-group(dot)com> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tom Ivar Helbekkmo <tih(at)nhh(dot)no>, pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] postmaster failure with 2-23 snapshot |
Date: | 1999-02-25 16:50:23 |
Message-ID: | 36D57F4F.A0FBEA09@ec-group.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker wrote:
> On Thu, 25 Feb 1999, Tom Lane wrote:
>
> Is there any way (sysctl?) of determining the max # of semaphores
> configured into a system?
Mark, I don't know if this is what you want, but with solaris, I can see what is
the current setup using "sysdef". At the end of the output, I have this:
*
* IPC Semaphores
*
128 entries in semaphore map (SEMMAP)
128 semaphore identifiers (SEMMNI)
8192 semaphores in system (SEMMNS)
8192 undo structures in system (SEMMNU)
64 max semaphores per id (SEMMSL)
32 max operations per semop call (SEMOPM)
32 max undo entries per process (SEMUME)
32767 semaphore maximum value (SEMVMX)
16384 adjust on exit max value (SEMAEM)
*
* IPC Shared Memory
*
16777216 max shared memory segment size (SHMMAX)
1 min shared memory segment size (SHMMIN)
100 shared memory identifiers (SHMMNI)
51 max attached shm segments per process (SHMSEG)
*
* Time Sharing Scheduler Tunables
*
60 maximum time sharing user priority (TSMAXUPRI)
SYS system class name (SYS_NAME)
--
Brian Millett
Enterprise Consulting Group "Heaven can not exist,
(314) 205-9030 If the family is not eternal"
bpm(at)ec-group(dot)com F. Ballard Washburn
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 1999-02-25 16:51:50 | Re: [HACKERS] postmaster failure with 2-23 snapshot |
Previous Message | Michael Davis | 1999-02-25 16:45:41 | RE: [INTERFACES] Foreign Keys |