From db1c6baeff0ca5c1d2ad94a7e514584b266ff480 Mon Sep 17 00:00:00 2001
From: Shigeru Hanada <shigeru.hanada@gmail.com>
Date: Wed, 29 Jun 2011 19:12:15 +0900
Subject: [PATCH] Revise document of force_not_null option.

Among FDW options for file_fdw, force_not_null is the only option which
has different specification from COPY's one.  COPY's one requires a list
of columns but file_fdw's one requires a boolean value.
---
 doc/src/sgml/file-fdw.sgml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/file-fdw.sgml b/doc/src/sgml/file-fdw.sgml
index 107476fa4c..b20d775426 100644
--- a/doc/src/sgml/file-fdw.sgml
+++ b/doc/src/sgml/file-fdw.sgml
@@ -122,10 +122,11 @@
 
    <listitem>
     <para>
-     Specifies that the column shouldn't been matched against the null string.
-     Acceptable values are <literal>true</> and <literal>falset</>
-     (case sensitive).
-     the same as <command>COPY</>'s <literal>FORCE_NOT_NULL</literal> option.
+     Specifies whether values for the column shouldn't been matched against
+     the null string.  Acceptable values are <literal>true</> for no matching,
+     and <literal>false</> for matching (case sensitive).
+     <literal>true</> is same as specifing the column in <command>COPY</>'s
+     <literal>FORCE_NOT_NULL</literal> option.
     </para>
    </listitem>
   </varlistentry>
-- 
2.39.5