<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.379 2007/03/06 09:54:23 petere Exp $ -->

<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.380 2007/03/06 09:59:22 petere Exp $ -->

<chapter Id="runtime">

<title>Operating System Environment</title>

<variablelist>

<varlistentry>

<term><systemitem class="osname">AIX</></term>

<indexterm><primary>AIX</><secondary>IPC configuration</></>

<listitem>

<para>

At least as of version 5.1, it should not be necessary to do

any special configuration for such parameters as

<varname>SHMMAX</varname>, as it appears this is configured to

allow all memory to be used as shared memory. That is the

sort of configuration commonly used for other databases such

as <application>DB/2</application>.</para>

<para> It might , however, be necessary to modify the global

<command>ulimit</command> information in

<filename>/etc/security/limits</filename>, as the default hard

limits for file sizes (<varname>fsize</varname>) and numbers of

files (<varname>nofiles</varname>) might be too low.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><systemitem class="osname">BSD/OS</></term>

<listitem>

<para>

The default settings are only suitable for small installations

(the defaultmax segment size is 32 MB). However the remaining

(the defaultmaximum segment size is 32 MB). However, the remaining

defaults are quite generously sized, and usually do not require

changes. Themax segment size can be changed via the

<command>sysctl</command> interface. For example, to allow 128 MB,

changes. Themaximum shared memory segment size can be changed via the

<command>sysctl</command> interface.For example, to allow 128 MB,

and explicitly set the maximum total shared memory size to 2097152

pages (the default):

<screen>

</listitem>

</varlistentry>

<varlistentry>

<term><systemitem class="osname">AIX</></term>

<indexterm><primary>AIX</><secondary>IPC configuration</></>

<listitem>

<para>

At least as of version 5.1, it should not be necessary to do

any special configuration for such parameters as

<varname>SHMMAX</varname>, as it appears this is configured to

allow all memory to be used as shared memory. That is the

sort of configuration commonly used for other databases such

as <application>DB/2</application>.</para>

<para> It might , however, be necessary to modify the global

<command>ulimit</command> information in

<filename>/etc/security/limits</filename>, as the default hard

limits for file sizes (<varname>fsize</varname>) and numbers of

files (<varname>nofiles</varname>) might be too low.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><systemitem class="osname">Solaris</></term>

<row>

<entry><xref linkend="guc-shared-buffers"></>

<entry>8300 (assuming8K <symbol>BLCKSZ</>)</entry>

<entry>8300 (assuming8 kB <symbol>BLCKSZ</>)</entry>

</row>

<row>

<entry><xref linkend="guc-wal-buffers"></>

<entry>8200 (assuming8K <symbol>XLOG_BLCKSZ</>)</entry>

<entry>8200 (assuming8 kB <symbol>XLOG_BLCKSZ</>)</entry>

</row>

<row>