Document the behavior of STRICT VARIADIC functions.

diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index ce6141107a7c2f817cccd16bf4a6600f034b4c71..a836d808c11918fcde2285f8a5b3d0c13d561cf0 100644 (file)
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.84.2.2 2009/10/02 18:13:10 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.84.2.3 2010/02/14 00:48:20 tgl Exp $
 -->
 
 <refentry id="SQL-CREATEFUNCTION">
@@ -570,6 +570,13 @@ CREATE FUNCTION foo(int, int default 42) ...
     to replace it (this includes being a member of the owning role).
    </para>
 
+   <para>
+    If a function is declared <literal>STRICT</> with a <literal>VARIADIC</>
+    argument, the strictness check tests that the variadic array <emphasis>as
+    a whole</> is non-null.  The function will still be called if the
+    array has non-null elements.
+   </para>
+
  </refsect1>
 
  <refsect1 id="sql-createfunction-examples">