Skip to content

Commit 5d924f0

Browse files
committed
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.
1 parent 869b1e4 commit 5d924f0

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

doc/src/sgml/ref/create_function.sgml

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -579,12 +579,13 @@ CREATE FUNCTION foo(int, int default 42) ...
579579

580580
<para>
581581
The full <acronym>SQL</acronym> type syntax is allowed for
582-
input arguments and return value. However, some details of the
583-
type specification (e.g., the precision field for
584-
type <type>numeric</type>) are the responsibility of the
585-
underlying function implementation and are silently swallowed
586-
(i.e., not recognized or
587-
enforced) by the <command>CREATE FUNCTION</command> command.
582+
declaring a function's arguments and return value. However,
583+
parenthesized type modifiers (e.g., the precision field for
584+
type <type>numeric</type>) are discarded by <command>CREATE FUNCTION</>.
585+
Thus for example
586+
<literal>CREATE FUNCTION foo (varchar(10)) ...</>
587+
is exactly the same as
588+
<literal>CREATE FUNCTION foo (varchar) ...</>.
588589
</para>
589590

590591
<para>

0 commit comments

Comments
 (0)