rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add documentation stating how to determine if FSM settings are too low 

--- look at a database-wide VACUUM VERBOSE.
This commit is contained in:
Bruce Momjian 2005-04-23 03:27:40 +00:00
parent e092828241
commit 25434e32cb
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/runtime.sgml
View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.314 2005/04/21 19:18:12 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.315 2005/04/23 03:27:40 momjian Exp $
-->
<chapter Id="runtime">
@ -1151,6 +1151,10 @@ SET ENABLE_SEQSCAN TO OFF;
be tracked in the shared free-space map. Six bytes of shared memory
are consumed for each page slot. This setting must be more than
16 * <varname>max_fsm_relations</varname>. The default is 20000.
The last few lines of a database-wide <command>VACUUM VERBOSE</>
can help in determining if the the default setting is suitable.
A <literal>NOTICE</> message is also printed during such an operation
if the current setting is too low.
This option can only be set at server start.
</para>
</listitem>
@ -1167,6 +1171,10 @@ SET ENABLE_SEQSCAN TO OFF;
free space will be tracked in the shared free-space map. Roughly
fifty bytes of shared memory are consumed for each slot.
The default is 1000.
The last few lines of a database-wide <command>VACUUM VERBOSE</>
can help in determining if the the default setting is suitable.
A <literal>NOTICE</> message is also printed during such an operation
if the current setting is too low.
This option can only be set at server start.
</para>
</listitem>