summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2013-11-13 18:29:45 +0000
committerTom Lane2013-11-13 18:29:45 +0000
commit0d6a006df6a3d57a3872d982a273e0e71f091dbd (patch)
treeb8005710acb9d1b5cd64f09bff23559d126a1ed4
parent8633aa9c3fa73dc9ba7ee5e78d7d5155e7710e0d (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 ebdcd8b01b8..c33bab8484a 100644
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -484,12 +484,13 @@ CREATE [ OR REPLACE ] FUNCTION
<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>