Add note about how each partition's default value is treated, into the doc.

Column defaults may be specified separately for each partition.
But INSERT via a partitioned table ignores those partition's default values.
The former is documented, but the latter restriction not.
This commit adds the note about that restriction into the document.

Back-patch to v10 where partitioning was introduced.

Author: Fujii Masao
Reviewed-by: Amit Langote
Discussion: https://postgr.es/m/CAHGQGwEs-59omrfGF7hOHz9iMME3RbKy5ny+iftDx3LHTEn9sA@mail.gmail.com

diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index 8836f04f54ee77d10d089a1c103aee6f39ae7b9d..8791672db4b16f95caaa41463606bc4c25d475da 100644 (file)
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -353,7 +353,8 @@ FROM ( { <replaceable class="PARAMETER">numeric_literal</replaceable> | <replace
       additional <literal>CHECK</> constraints; additional constraints with
       the same name and condition as in the parent will be merged with the
       parent constraint.  Defaults may be specified separately for each
-      partition.
+      partition. But note that a partition's default value is not applied
+      when inserting a tuple through a partitioned table.
      </para>
 
      <para>