postgres.git / summary / log / commit / refs
commit a1c29c1fe153302c41c6c90815a5d73f2ceeb8a5
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed Nov 13 18:26:33 2013 +0000
First released in: 9.4.0, 8.4.19, 9.0.15, 9.1.11, 9.2.6, 9.3.2
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.
doc/src/sgml/ref/create_function.sgml | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index a679a853a99..81278bb2f81 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>
[parent: 2720c55c0986]