summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2013-11-13 13:26:33 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2013-11-13 13:26:44 -0500
commit42f8e268c9b3e89dbb50c2dabdef5109655248ae (patch)
treefc0bf2c477f66002f121e02ccea124eb57d6292a
parentd147aedbfedf210e676c5c59166d32af1de79e1f (diff)
Clarify CREATE FUNCTION documentation about handling of typmods.
The previous text was a bit misleading, as well as unnecessarily vague about what information would be discarded. Per gripe from Craig Skinner.
-rw-r--r--doc/src/sgml/ref/create_function.sgml13
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index f42bd489660..c82fbdca7a1 100644
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -579,12 +579,13 @@ CREATE FUNCTION foo(int, int default 42) ...
<para>
The full <acronym>SQL</acronym> type syntax is allowed for
- input arguments and return value. However, some details of the
- type specification (e.g., the precision field for
- type <type>numeric</type>) are the responsibility of the
- underlying function implementation and are silently swallowed
- (i.e., not recognized or
- enforced) by the <command>CREATE FUNCTION</command> command.
+ declaring a function's arguments and return value. However,
+ parenthesized type modifiers (e.g., the precision field for
+ type <type>numeric</type>) are discarded by <command>CREATE FUNCTION</>.
+ Thus for example
+ <literal>CREATE FUNCTION foo (varchar(10)) ...</>
+ is exactly the same as
+ <literal>CREATE FUNCTION foo (varchar) ...</>.
</para>
<para>