From 25434e32cb1cf4e7c61a21482832ecc5b33e1f5a Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 23 Apr 2005 03:27:40 +0000
Subject: [PATCH] Add documentation stating how to determine if FSM settings
are too low --- look at a database-wide VACUUM VERBOSE.
---
doc/src/sgml/runtime.sgml | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 72bc1ff17e..cb527bedbc 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -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>
--
2.40.0