From 53e3f9dcfdb533dc4513c35d4d2e090eed81f6c2 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 1 Nov 2007 17:06:30 +0000
Subject: [PATCH] Add documentation mention that FSM == Free Space Map, so the
config parameter name makes more sense.
---
doc/src/sgml/config.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index e05685dd92b..0d11754905d 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.151 2007/10/20 04:00:38 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.152 2007/11/01 17:06:30 momjian Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
@@ -891,7 +891,7 @@ SET ENABLE_SEQSCAN TO OFF;
<para>
These parameters control the size of the shared <firstterm>free space
- map</>, which tracks the locations of unused space in the database.
+ map</> (<acronym>FSM</>), which tracks the locations of unused space in the database.
An undersized free space map can cause the database to consume
increasing amounts of disk space over time, because free space that
is not in the map cannot be re-used; instead <productname>PostgreSQL</>
--
GitLab