postgres.git / summary / log / commit / refs

commit    3c871d1ead20e6744403e2180d704dd09fd8c2d6
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue Mar 17 19:05:17 2020 +0000
First released in: 13.0, 9.5.22, 9.6.18, 10.13, 11.8, 12.3

    Doc: clarify behavior of "anyrange" pseudo-type.
    
    I noticed that we completely failed to document the restriction
    that an "anyrange" result type has to be inferred from an "anyrange"
    input.  The docs also were less clear than they could be about the
    relationship between "anyrange" and "anyarray".
    
    It's been like this all along, so back-patch.


doc/src/sgml/extend.sgml | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 2e3b5f678e7..8c68d595e52 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -225,10 +225,12 @@ <type>anyarray</type> positions must be an array whose elements are the same type appearing in the <type>anyelement</type> positions. Similarly, if there are positions declared <type>anyrange</type> - and others declared <type>anyelement</type>, the actual range type in - the <type>anyrange</type> positions must be a range whose subtype is - the same type appearing in the <type>anyelement</type> positions. - <type>anynonarray</> is treated exactly the same as <type>anyelement</>, + and others declared <type>anyelement</type> or <type>anyarray</type>, + the actual range type in the <type>anyrange</type> positions must be a + range whose subtype is the same type appearing in + the <type>anyelement</type> positions and the same as the element type + of the <type>anyarray</type> positions. + <type>anynonarray</type> is treated exactly the same as <type>anyelement</type>, but adds the additional constraint that the actual type must not be an array type. <type>anyenum</> is treated exactly the same as <type>anyelement</>, @@ -258,6 +260,17 @@ will only accept arrays of enum types. </para> + <para> + In most cases, the parser can infer the actual data type for a + polymorphic result type from arguments that are of a different + polymorphic type; for example <type>anyarray</type> can be deduced + from <type>anyelement</type> or vice versa. The exception is that a + polymorphic result of type <type>anyrange</type> requires an argument + of type <type>anyrange</type>; it cannot be deduced + from <type>anyarray</type> or <type>anyelement</type> arguments. This + is because there could be multiple range types with the same subtype. + </para> + <para> Note that <type>anynonarray</> and <type>anyenum</> do not represent separate type variables; they are the same type as [parent: d67d7243f914]