I have applied the following patch suggesting people look at the last
few lines of a database-wide VACUUM VERBOSE to determine if the current
setting is appropriate. Also mention the NOTICE that is printed if it
is too low.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Index: doc/src/sgml/runtime.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v
retrieving revision 1.314
diff -c -c -r1.314 runtime.sgml
*** doc/src/sgml/runtime.sgml 21 Apr 2005 19:18:12 -0000 1.314
--- doc/src/sgml/runtime.sgml 23 Apr 2005 03:26:18 -0000
***************
*** 1151,1156 ****
--- 1151,1160 ----
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,1172 ****
--- 1171,1180 ----
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>
