Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
cee63eab
Commit
cee63eab
authored
16 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update documentation table describing how shared memory is used by
various facilities.
parent
a666d285
No related branches found
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/runtime.sgml
+19
-25
19 additions, 25 deletions
doc/src/sgml/runtime.sgml
with
19 additions
and
25 deletions
doc/src/sgml/runtime.sgml
+
19
−
25
View file @
cee63eab
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.42
3
2008/12/1
6
1
9:30:43 alvherre
Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.42
4
2008/12/1
8
1
7:03:09 momjian
Exp $ -->
<chapter Id="runtime">
<title>Operating System Environment</title>
...
...
@@ -1080,41 +1080,45 @@ set semsys:seminfo_semmsl=32
<table id="shared-memory-parameters">
<title>Configuration parameters affecting
<productname>PostgreSQL</productname>'s shared memory usage</>
<title><productname>PostgreSQL</productname> shared memory usage</>
<tgroup cols="2">
<thead>
<row>
<entry>
Nam
e</>
<entry>Approximate
multiplier (bytes per increment)
as of 8.3</>
<entry>
Usag
e</>
<entry>Approximate
shared memory bytes required (
as of 8.3
)
</>
</row>
</thead>
<tbody>
<row>
<entry><xref linkend="guc-max-connections"></>
<entry>1800 + 270 * <xref linkend="guc-max-locks-per-transaction"></entry>
<entry>Connections</>
<entry>(1800 + 270 * <xref
linkend="guc-max-locks-per-transaction">) * <xref
linkend="guc-max-connections"></entry>
</row>
<row>
<entry><xref linkend="guc-autovacuum-max-workers"></>
<entry>1800 + 270 * <xref linkend="guc-max-locks-per-transaction"></entry>
<entry>Autovacuum workers</>
<entry>(1800 + 270 * <xref
linkend="guc-max-locks-per-transaction">) * <xref
linkend="guc-autovacuum-max-workers"></entry>
</row>
<row>
<entry><xref linkend="guc-max-prepared-transactions"></>
<entry>770 + 270 * <xref linkend="guc-max-locks-per-transaction"></entry>
<entry>Prepared transactions</>
<entry>(770 + 270 * <xref
linkend="guc-max-locks-per-transaction">) * <xref linkend="guc-max-prepared-transactions"></entry>
</row>
<row>
<entry>
<xref linkend="guc-shared-
buffers
">
</>
<entry>
8400 (assuming 8 kB <symbol>BLCKSZ</>)
</entry>
<entry>
Shared disk
buffers</>
<entry>
(<xref linkend="guc-block-size"> + 208) * <xref linkend="guc-shared-buffers">
</entry>
</row>
<row>
<entry>
<xref linkend="guc-wal-
buffers
">
</>
<entry>
8200 (assuming 8 kB <symbol>XLOG_BLCKSZ</>)
</entry>
<entry>
WAL
buffers</>
<entry>
(<xref linkend="guc-wal-block-size"> + 8) * <xref linkend="guc-wal-buffers">
</entry>
</row>
<row>
...
...
@@ -1125,18 +1129,8 @@ set semsys:seminfo_semmsl=32
</tgroup>
</table>
<note>
<para>
The multipliers for <varname>shared_buffers</> and
<varname>wal_buffers</> should be the number of buffers, not the
amount in bytes. To find out the number of shared or wal buffers, divide
the amount in bytes by <xref linkend="guc-block-size"> and
<xref linkend="guc-wal-block-size">, respectively.
</para>
</note>
</sect2>
<sect2>
<title>Resource Limits</title>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment