Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
83993240
Commit
83993240
authored
Nov 10, 2000
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos.
parent
27026fef
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
15 deletions
+15
-15
doc/src/sgml/runtime.sgml
doc/src/sgml/runtime.sgml
+15
-15
No files found.
doc/src/sgml/runtime.sgml
View file @
83993240
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.3
2 2000/11/08 17:57:45 petere
Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.3
3 2000/11/10 16:32:09 tgl
Exp $
-->
<Chapter Id="runtime">
...
...
@@ -1217,12 +1217,12 @@ env PGOPTIONS='-c geqo=off' psql
limits of the IPC resources then the postmaster will refuse to
start up and should leave a marginally instructive error message
about which problem was encountered and what needs to be done
about it. The relevant kernel parameters
have a relatively
consistent
nomenclature across
systems; <xref
about it. The relevant kernel parameters
are named
consistent
ly across different
systems; <xref
linkend="sysvipc-parameters"> gives an overview. The methods to
set them, however, vary; suggestions for some platforms are given
below. Be aware
, however,
that you will have to reboot your
machine at
best, or possibly
recompile the kernel, to change these
below. Be aware that you will have to reboot your
machine at
least, possibly even
recompile the kernel, to change these
settings.
</para>
...
...
@@ -1255,7 +1255,7 @@ env PGOPTIONS='-c geqo=off' psql
<row>
<entry><varname>SHMSEG</></>
<entry>Maximum number of shared memory segments per process</>
<entry>
Must be at least 3, but the default is much higher.
</>
<entry>
must be at least 3, but the default is much higher
</>
</row>
<row>
...
...
@@ -1267,13 +1267,13 @@ env PGOPTIONS='-c geqo=off' psql
<row>
<entry><varname>SEMMNI</></>
<entry>Maximum number of semaphore identifiers (i.e., sets)</>
<entry>>= ceil(max_connections
%
16)</>
<entry>>= ceil(max_connections
/
16)</>
</row>
<row>
<entry><varname>SEMMNS</></>
<entry>Maximum number of semaphores system-wide</>
<entry>
number of allowed connections, rounded up to multiple of 16
</>
<entry>
max_connections rounded up to multiple of 16, + room for other applications
</>
</row>
<row>
...
...
@@ -1337,7 +1337,7 @@ env PGOPTIONS='-c geqo=off' psql
The parameter <varname>SEMMNI</> determines the limit on the
number of semaphore sets that can exist on the system at one time.
Hence this parameter must be at least
<literal>ceil(max_connections
%
16)</>. Lowering the number of
<literal>ceil(max_connections
/
16)</>. Lowering the number of
allowed connections is a temporary workaround for failures, which
are usually confusingly worded <quote><errorname>No space left on
device</></>, from the function <function>semget()</>.
...
...
@@ -1351,7 +1351,7 @@ env PGOPTIONS='-c geqo=off' psql
semaphores needs an entry. When a semaphore set is freed it is
either added to an existing entry that is adjacent to the freed
block or it is registered under a new map entry. If the map is
full, the freed semaphores get
s
lost (until reboot). Fragmentation
full, the freed semaphores get lost (until reboot). Fragmentation
of the semaphore space could therefore over time lead to less
available semaphores than there should be.
</para>
...
...
@@ -1363,9 +1363,9 @@ env PGOPTIONS='-c geqo=off' psql
</para>
<para>
Various settings related to <quote>semaphore undo</>, such as
<varname>SEMMNU</> and <varname>SEMUME</>, are not of
relevance
with
<productname>Postgres</>.
Various
other
settings related to <quote>semaphore undo</>, such as
<varname>SEMMNU</> and <varname>SEMUME</>, are not of
concern
for
<productname>Postgres</>.
</para>
...
...
@@ -1386,7 +1386,7 @@ env PGOPTIONS='-c geqo=off' psql
<programlisting>
/sys/sys/shm.h:69:#define SHMMAXPGS 1024 /* max hardware pages... */
</programlisting>
The default setting of 1024
is for
a maximum of 4 MB of shared
The default setting of 1024
provides
a maximum of 4 MB of shared
memory.
</para>
</formalpara>
...
...
@@ -1457,7 +1457,7 @@ options "SEMMNU=120"
to be enabled when the kernel is compiled. (They are by
default.) The maximum size of shared memory is determined by
the option <varname>SHMMAXPGS</> (in pages). The following
shows an example o
n
how to set the various parameters:
shows an example o
f
how to set the various parameters:
<programlisting>
options SYSVSHM
options SHMMAXPGS=4096
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment