From f1e237b6b2e1199cdda995dd655c68b0174c8fdb Mon Sep 17 00:00:00 2001
From: Magnus Hagander <magnus@hagander.net>
Date: Mon, 25 Aug 2008 18:55:43 +0000
Subject: Unconditionally write the statsfile when SIGHUP is received, to
 minimize the window during which backends have no statistics file to read.

---
 doc/src/sgml/config.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 3eca0bab845..757ee2a3dbc 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.188 2008/08/25 15:11:00 mha Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.189 2008/08/25 18:55:43 mha Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -3419,8 +3419,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
         <filename>pg_stat_tmp</filename>. Pointing this at a RAM based filesystem
         will decrease physical I/O requirements and can lead to increased 
         performance. If this parameter is changed when the system is running,
-        the statistics functions might return no information until a new 
-        file has been written, which typically happens twice per second.
+		there is a small window of time until the new file has been written 
+		during which the statistics functions might return no information.
        </para>
       </listitem>
      </varlistentry>
-- 
cgit v1.2.3