Re: [HACKERS] PostgreSQL and Solaris 7?

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, "Daryl W(dot) Dunbar" <daryl(at)www(dot)com>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] PostgreSQL and Solaris 7?
Date: 1999-02-10 08:56:50
Message-ID: 199902100856.RAA28117@srapc451.sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> Increasing # of semaphores should solve the problem, I guess. I'm
>> going to try that as soon as I find the way to increase semaphores.
>
>>From oen of our servers at work, using Oracle
>
>/etc/system:
>
>set shmsys:shminfo_shmmax=16777216
>set shmsys:shminfo_shmmin=1
>set shmsys:shminfo_shmmni=100
>set shmsys:shminfo_shmseg=51
>
>
>There are appropriate values for sem also...I actually have a document at
>work that explains it all...let me see if I can dig it up and add it to
>the WWW site or something...

Great.

I checked my Solaris box using sysdef and got:

* IPC Semaphores
*
10 entries in semaphore map (SEMMAP)
10 semaphore identifiers (SEMMNI)
60 semaphores in system (SEMMNS)
30 undo structures in system (SEMMNU)
25 max semaphores per id (SEMMSL)
10 max operations per semop call (SEMOPM)
10 max undo entries per process (SEMUME)
32767 semaphore maximum value (SEMVMX)
16384 adjust on exit max value (SEMAEM)

There are so many tunable paramters! I expect cleaner explanations for
these kernel variables from Marc's document.
--
Tatsuo Ishii

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 1999-02-10 08:59:01 Re: [HACKERS] cannot cast bpchar and varchar
Previous Message Oleg Broytmann 1999-02-10 08:20:32 Re: [HACKERS] PostgreSQL and Solaris 7?