summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 5d0c2d5)
raw | patch | inline | side by side (parent: 5d0c2d5)
| author | Tom Lane <tgl@sss.pgh.pa.us> | |
| Tue, 17 Mar 2020 22:29:07 +0000 (18:29 -0400) | ||
| committer | Tom Lane <tgl@sss.pgh.pa.us> | |
| Tue, 17 Mar 2020 22:29:14 +0000 (18:29 -0400) |
Ordinarily it's impossible for an actual input of a function to have
declared type ANYARRAY, since we'd resolve that to a concrete array
type before doing argument type resolution for the function. But an
exception arises for functions applied to certain columns of pg_statistic
or pg_stats, since we abuse the "anyarray" pseudotype by using it to
declare those columns. So parse_coerce.c has to deal with the case.
Previously we allowed an ANYARRAY actual input to match an ANYARRAY
polymorphic argument, but only if no other argument or result was
declared ANYELEMENT. When that logic was written, those were the only
two polymorphic types, and I fear nobody thought carefully about how it
ought to extend to the other ones that came along later. But actually
it was wrong even then, because if a function has two ANYARRAY
arguments, it should be able to expect that they have identical element
types, and we'd not be able to ensure that.
The correct generalization is that we can match an ANYARRAY actual input
to an ANYARRAY polymorphic argument only if no other argument or result
is of any polymorphic type, so that no promises are being made about
element type compatibility. check_generic_type_consistency can't test
that condition, but it seems better anyway to accept such matches there
and then throw an error if needed in enforce_generic_type_consistency.
That way we can produce a specific error message rather than an
unintuitive "function does not exist" complaint. (There's some risk
perhaps of getting new ambiguous-function complaints, but I think that
any set of functions for which that could happen would be ambiguous
against ordinary array columns as well.) While we're at it, we can
improve the message that's produced in cases that the code did already
object to, as shown in the regression test changes.
Also, remove a similar test that got cargo-culted in for ANYRANGE;
there are no catalog columns of type ANYRANGE, and I hope we never
create any, so that's not needed. (It was incomplete anyway.)
While here, update some comments and rearrange the code a bit in
preparation for upcoming additions of more polymorphic types.
In practical situations I believe this is just exchanging one error
message for another, hopefully better, one. So it doesn't seem
needful to back-patch, even though the mistake is ancient.
Discussion: https://postgr.es/m/21569.1584314271@sss.pgh.pa.us
declared type ANYARRAY, since we'd resolve that to a concrete array
type before doing argument type resolution for the function. But an
exception arises for functions applied to certain columns of pg_statistic
or pg_stats, since we abuse the "anyarray" pseudotype by using it to
declare those columns. So parse_coerce.c has to deal with the case.
Previously we allowed an ANYARRAY actual input to match an ANYARRAY
polymorphic argument, but only if no other argument or result was
declared ANYELEMENT. When that logic was written, those were the only
two polymorphic types, and I fear nobody thought carefully about how it
ought to extend to the other ones that came along later. But actually
it was wrong even then, because if a function has two ANYARRAY
arguments, it should be able to expect that they have identical element
types, and we'd not be able to ensure that.
The correct generalization is that we can match an ANYARRAY actual input
to an ANYARRAY polymorphic argument only if no other argument or result
is of any polymorphic type, so that no promises are being made about
element type compatibility. check_generic_type_consistency can't test
that condition, but it seems better anyway to accept such matches there
and then throw an error if needed in enforce_generic_type_consistency.
That way we can produce a specific error message rather than an
unintuitive "function does not exist" complaint. (There's some risk
perhaps of getting new ambiguous-function complaints, but I think that
any set of functions for which that could happen would be ambiguous
against ordinary array columns as well.) While we're at it, we can
improve the message that's produced in cases that the code did already
object to, as shown in the regression test changes.
Also, remove a similar test that got cargo-culted in for ANYRANGE;
there are no catalog columns of type ANYRANGE, and I hope we never
create any, so that's not needed. (It was incomplete anyway.)
While here, update some comments and rearrange the code a bit in
preparation for upcoming additions of more polymorphic types.
In practical situations I believe this is just exchanging one error
message for another, hopefully better, one. So it doesn't seem
needful to back-patch, even though the mistake is ancient.
Discussion: https://postgr.es/m/21569.1584314271@sss.pgh.pa.us
index 4a2b463d1b7fc068158b805eebb42a7c7d317079..f1afd8fca327fc97b5598ad0eb8bf348e03f17a0 100644 (file)
* which must be a varlena array type.
* 3) All arguments declared ANYRANGE must have the same datatype,
* which must be a range type.
- * 4) If there are arguments of both ANYELEMENT and ANYARRAY, make sure the
- * actual ANYELEMENT datatype is in fact the element type for the actual
- * ANYARRAY datatype.
- * 5) Similarly, if there are arguments of both ANYELEMENT and ANYRANGE,
- * make sure the actual ANYELEMENT datatype is in fact the subtype for
- * the actual ANYRANGE type.
- * 6) ANYENUM is treated the same as ANYELEMENT except that if it is used
+ * 4) If there are arguments of more than one of these polymorphic types,
+ * the array element type and/or range subtype must be the same as each
+ * other and the same as the ANYELEMENT type.
+ * 5) ANYENUM is treated the same as ANYELEMENT except that if it is used
* (alone or in combination with plain ANYELEMENT), we add the extra
* condition that the ANYELEMENT type must be an enum.
- * 7) ANYNONARRAY is treated the same as ANYELEMENT except that if it is used,
+ * 6) ANYNONARRAY is treated the same as ANYELEMENT except that if it is used,
* we add the extra condition that the ANYELEMENT type must not be an array.
* (This is a no-op if used in combination with ANYARRAY or ANYENUM, but
* is an extra restriction if not.)
* If we have UNKNOWN input (ie, an untyped literal) for any polymorphic
* argument, assume it is okay.
*
- * If an input is of type ANYARRAY (ie, we know it's an array, but not
- * what element type), we will accept it as a match to an argument declared
- * ANYARRAY, so long as we don't have to determine an element type ---
- * that is, so long as there is no use of ANYELEMENT. This is mostly for
- * backwards compatibility with the pre-7.4 behavior of ANYARRAY.
- *
* We do not ereport here, but just return false if a rule is violated.
*/
bool
const Oid *declared_arg_types,
int nargs)
{
- int j;
Oid elem_typeid = InvalidOid;
Oid array_typeid = InvalidOid;
- Oid array_typelem;
Oid range_typeid = InvalidOid;
- Oid range_typelem;
- bool have_anyelement = false;
bool have_anynonarray = false;
bool have_anyenum = false;
* Loop through the arguments to see if we have any that are polymorphic.
* If so, require the actual types to be consistent.
*/
- for (j = 0; j < nargs; j++)
+ for (int j = 0; j < nargs; j++)
{
Oid decl_type = declared_arg_types[j];
Oid actual_type = actual_arg_types[j];
decl_type == ANYNONARRAYOID ||
decl_type == ANYENUMOID)
{
- have_anyelement = true;
if (decl_type == ANYNONARRAYOID)
have_anynonarray = true;
else if (decl_type == ANYENUMOID)
if (OidIsValid(array_typeid))
{
if (array_typeid == ANYARRAYOID)
- {
- /* Special case for ANYARRAY input: okay iff no ANYELEMENT */
- if (have_anyelement)
- return false;
- return true;
- }
-
- array_typelem = get_element_type(array_typeid);
- if (!OidIsValid(array_typelem))
- return false; /* should be an array, but isn't */
-
- if (!OidIsValid(elem_typeid))
{
/*
- * if we don't have an element type yet, use the one we just got
+ * Special case for matching ANYARRAY input to an ANYARRAY
+ * argument: allow it for now. enforce_generic_type_consistency()
+ * might complain later, depending on the presence of other
+ * polymorphic arguments or results, but it will deliver a less
+ * surprising error message than "function does not exist".
+ *
+ * (If you think to change this, note that can_coerce_type will
+ * consider such a situation as a match, so that we might not even
+ * get here.)
*/
- elem_typeid = array_typelem;
}
- else if (array_typelem != elem_typeid)
+ else
{
- /* otherwise, they better match */
- return false;
+ Oid array_typelem;
+
+ array_typelem = get_element_type(array_typeid);
+ if (!OidIsValid(array_typelem))
+ return false; /* should be an array, but isn't */
+
+ if (!OidIsValid(elem_typeid))
+ {
+ /*
+ * if we don't have an element type yet, use the one we just
+ * got
+ */
+ elem_typeid = array_typelem;
+ }
+ else if (array_typelem != elem_typeid)
+ {
+ /* otherwise, they better match */
+ return false;
+ }
}
}
/* Get the element type based on the range type, if we have one */
if (OidIsValid(range_typeid))
{
+ Oid range_typelem;
+
range_typelem = get_range_subtype(range_typeid);
if (!OidIsValid(range_typelem))
return false; /* should be a range, but isn't */
* Rules are applied to the function's return type (possibly altering it)
* if it is declared as a polymorphic type:
*
- * 1) If return type is ANYARRAY, and any argument is ANYARRAY, use the
+ * 1) If return type is ANYELEMENT, and any argument is ANYELEMENT, use the
* argument's actual type as the function's return type.
- * 2) Similarly, if return type is ANYRANGE, and any argument is ANYRANGE,
- * use the argument's actual type as the function's return type.
- * 3) If return type is ANYARRAY, no argument is ANYARRAY, but any argument is
- * ANYELEMENT, use the actual type of the argument to determine the
- * function's return type, i.e. the element type's corresponding array
- * type. (Note: similar behavior does not exist for ANYRANGE, because it's
- * impossible to determine the range type from the subtype alone.)
- * 4) If return type is ANYARRAY, but no argument is ANYARRAY or ANYELEMENT,
- * generate an error. Similarly, if return type is ANYRANGE, but no
- * argument is ANYRANGE, generate an error. (These conditions are
- * prevented by CREATE FUNCTION and therefore are not expected here.)
- * 5) If return type is ANYELEMENT, and any argument is ANYELEMENT, use the
+ * 2) If return type is ANYARRAY, and any argument is ANYARRAY, use the
* argument's actual type as the function's return type.
- * 6) If return type is ANYELEMENT, no argument is ANYELEMENT, but any argument
- * is ANYARRAY or ANYRANGE, use the actual type of the argument to determine
- * the function's return type, i.e. the array type's corresponding element
- * type or the range type's corresponding subtype (or both, in which case
- * they must match).
- * 7) If return type is ANYELEMENT, no argument is ANYELEMENT, ANYARRAY, or
- * ANYRANGE, generate an error. (This condition is prevented by CREATE
- * FUNCTION and therefore is not expected here.)
- * 8) ANYENUM is treated the same as ANYELEMENT except that if it is used
+ * 3) Similarly, if return type is ANYRANGE, and any argument is ANYRANGE,
+ * use the argument's actual type as the function's return type.
+ * 4) Otherwise, if return type is ANYELEMENT or ANYARRAY, there should be
+ * at least one ANYELEMENT, ANYARRAY, or ANYRANGE input; deduce the
+ * return type from those inputs, or throw error if we can't.
+ * 5) Otherwise, if return type is ANYRANGE, throw error. (There should
+ * be at least one ANYRANGE input, since CREATE FUNCTION enforces that.)
+ * 6) ANYENUM is treated the same as ANYELEMENT except that if it is used
* (alone or in combination with plain ANYELEMENT), we add the extra
* condition that the ANYELEMENT type must be an enum.
- * 9) ANYNONARRAY is treated the same as ANYELEMENT except that if it is used,
+ * 7) ANYNONARRAY is treated the same as ANYELEMENT except that if it is used,
* we add the extra condition that the ANYELEMENT type must not be an array.
* (This is a no-op if used in combination with ANYARRAY or ANYENUM, but
* is an extra restriction if not.)
*
* Domains over arrays or ranges match ANYARRAY or ANYRANGE arguments,
- * respectively, and are immediately flattened to their base type. (In
- * particular, if the return type is also ANYARRAY or ANYRANGE, we'll set it
- * to the base type not the domain type.)
+ * respectively, and are immediately flattened to their base type. (In
+ * particular, if the return type is also ANYARRAY or ANYRANGE, we'll set
+ * it to the base type not the domain type.)
*
* When allow_poly is false, we are not expecting any of the actual_arg_types
* to be polymorphic, and we should not return a polymorphic result type
* either. When allow_poly is true, it is okay to have polymorphic "actual"
- * arg types, and we can return ANYARRAY, ANYRANGE, or ANYELEMENT as the
- * result. (This case is currently used only to check compatibility of an
- * aggregate's declaration with the underlying transfn.)
+ * arg types, and we can return a matching polymorphic type as the result.
+ * (This case is currently used only to check compatibility of an aggregate's
+ * declaration with the underlying transfn.)
*
* A special case is that we could see ANYARRAY as an actual_arg_type even
* when allow_poly is false (this is possible only because pg_statistic has
* columns shown as anyarray in the catalogs). We allow this to match a
- * declared ANYARRAY argument, but only if there is no ANYELEMENT argument
- * or result (since we can't determine a specific element type to match to
- * ANYELEMENT). Note this means that functions taking ANYARRAY had better
- * behave sanely if applied to the pg_statistic columns; they can't just
- * assume that successive inputs are of the same actual element type.
+ * declared ANYARRAY argument, but only if there is no other polymorphic
+ * argument that we would need to match it with, and no need to determine
+ * the element type to infer the result type. Note this means that functions
+ * taking ANYARRAY had better behave sanely if applied to the pg_statistic
+ * columns; they can't just assume that successive inputs are of the same
+ * actual element type.
*/
Oid
enforce_generic_type_consistency(const Oid *actual_arg_types,
Oid rettype,
bool allow_poly)
{
- int j;
- bool have_generics = false;
- bool have_unknowns = false;
+ bool have_poly_unknowns = false;
Oid elem_typeid = InvalidOid;
Oid array_typeid = InvalidOid;
Oid range_typeid = InvalidOid;
- Oid array_typelem;
- Oid range_typelem;
- bool have_anyelement = (rettype == ANYELEMENTOID ||
- rettype == ANYNONARRAYOID ||
- rettype == ANYENUMOID);
+ int n_poly_args = 0;
bool have_anynonarray = (rettype == ANYNONARRAYOID);
bool have_anyenum = (rettype == ANYENUMOID);
* Loop through the arguments to see if we have any that are polymorphic.
* If so, require the actual types to be consistent.
*/
- for (j = 0; j < nargs; j++)
+ for (int j = 0; j < nargs; j++)
{
Oid decl_type = declared_arg_types[j];
Oid actual_type = actual_arg_types[j];
decl_type == ANYNONARRAYOID ||
decl_type == ANYENUMOID)
{
- have_generics = have_anyelement = true;
+ n_poly_args++;
if (decl_type == ANYNONARRAYOID)
have_anynonarray = true;
else if (decl_type == ANYENUMOID)
have_anyenum = true;
if (actual_type == UNKNOWNOID)
{
- have_unknowns = true;
+ have_poly_unknowns = true;
continue;
}
if (allow_poly && decl_type == actual_type)
}
else if (decl_type == ANYARRAYOID)
{
- have_generics = true;
+ n_poly_args++;
if (actual_type == UNKNOWNOID)
{
- have_unknowns = true;
+ have_poly_unknowns = true;
continue;
}
if (allow_poly && decl_type == actual_type)
}
else if (decl_type == ANYRANGEOID)
{
- have_generics = true;
+ n_poly_args++;
if (actual_type == UNKNOWNOID)
{
- have_unknowns = true;
+ have_poly_unknowns = true;
continue;
}
if (allow_poly && decl_type == actual_type)
* Fast Track: if none of the arguments are polymorphic, return the
* unmodified rettype. We assume it can't be polymorphic either.
*/
- if (!have_generics)
+ if (n_poly_args == 0)
+ {
+ Assert(!IsPolymorphicType(rettype));
return rettype;
+ }
- /* Get the element type based on the array type, if we have one */
- if (OidIsValid(array_typeid))
+ if (n_poly_args)
{
- if (array_typeid == ANYARRAYOID && !have_anyelement)
- {
- /* Special case for ANYARRAY input: okay iff no ANYELEMENT */
- array_typelem = ANYELEMENTOID;
- }
- else
+ /* Get the element type based on the array type, if we have one */
+ if (OidIsValid(array_typeid))
{
- array_typelem = get_element_type(array_typeid);
- if (!OidIsValid(array_typelem))
+ Oid array_typelem;
+
+ if (array_typeid == ANYARRAYOID)
+ {
+ /*
+ * Special case for matching ANYARRAY input to an ANYARRAY
+ * argument: allow it iff no other arguments are polymorphic
+ * (otherwise we couldn't be sure whether the array element
+ * type matches up) and the result type doesn't require us to
+ * infer a specific element type.
+ */
+ if (n_poly_args != 1 ||
+ (rettype != ANYARRAYOID && IsPolymorphicType(rettype)))
+ ereport(ERROR,
+ (errcode(ERRCODE_DATATYPE_MISMATCH),
+ errmsg("cannot determine element type of \"anyarray\" argument")));
+ array_typelem = ANYELEMENTOID;
+ }
+ else
+ {
+ array_typelem = get_element_type(array_typeid);
+ if (!OidIsValid(array_typelem))
+ ereport(ERROR,
+ (errcode(ERRCODE_DATATYPE_MISMATCH),
+ errmsg("argument declared %s is not an array but type %s",
+ "anyarray", format_type_be(array_typeid))));
+ }
+
+ if (!OidIsValid(elem_typeid))
+ {
+ /*
+ * if we don't have an element type yet, use the one we just
+ * got
+ */
+ elem_typeid = array_typelem;
+ }
+ else if (array_typelem != elem_typeid)
+ {
+ /* otherwise, they better match */
ereport(ERROR,
(errcode(ERRCODE_DATATYPE_MISMATCH),
- errmsg("argument declared %s is not an array but type %s",
- "anyarray", format_type_be(array_typeid))));
+ errmsg("argument declared %s is not consistent with argument declared %s",
+ "anyarray", "anyelement"),
+ errdetail("%s versus %s",
+ format_type_be(array_typeid),
+ format_type_be(elem_typeid))));
+ }
}
- if (!OidIsValid(elem_typeid))
- {
- /*
- * if we don't have an element type yet, use the one we just got
- */
- elem_typeid = array_typelem;
- }
- else if (array_typelem != elem_typeid)
+ /* Get the element type based on the range type, if we have one */
+ if (OidIsValid(range_typeid))
{
- /* otherwise, they better match */
- ereport(ERROR,
- (errcode(ERRCODE_DATATYPE_MISMATCH),
- errmsg("argument declared %s is not consistent with argument declared %s",
- "anyarray", "anyelement"),
- errdetail("%s versus %s",
- format_type_be(array_typeid),
- format_type_be(elem_typeid))));
- }
- }
+ Oid range_typelem;
- /* Get the element type based on the range type, if we have one */
- if (OidIsValid(range_typeid))
- {
- if (range_typeid == ANYRANGEOID && !have_anyelement)
- {
- /* Special case for ANYRANGE input: okay iff no ANYELEMENT */
- range_typelem = ANYELEMENTOID;
- }
- else
- {
range_typelem = get_range_subtype(range_typeid);
if (!OidIsValid(range_typelem))
ereport(ERROR,
errmsg("argument declared %s is not a range type but type %s",
"anyrange",
format_type_be(range_typeid))));
+
+ if (!OidIsValid(elem_typeid))
+ {
+ /*
+ * if we don't have an element type yet, use the one we just
+ * got
+ */
+ elem_typeid = range_typelem;
+ }
+ else if (range_typelem != elem_typeid)
+ {
+ /* otherwise, they better match */
+ ereport(ERROR,
+ (errcode(ERRCODE_DATATYPE_MISMATCH),
+ errmsg("argument declared %s is not consistent with argument declared %s",
+ "anyrange", "anyelement"),
+ errdetail("%s versus %s",
+ format_type_be(range_typeid),
+ format_type_be(elem_typeid))));
+ }
}
if (!OidIsValid(elem_typeid))
{
- /*
- * if we don't have an element type yet, use the one we just got
- */
- elem_typeid = range_typelem;
- }
- else if (range_typelem != elem_typeid)
- {
- /* otherwise, they better match */
- ereport(ERROR,
- (errcode(ERRCODE_DATATYPE_MISMATCH),
- errmsg("argument declared %s is not consistent with argument declared %s",
- "anyrange", "anyelement"),
- errdetail("%s versus %s",
- format_type_be(range_typeid),
- format_type_be(elem_typeid))));
+ if (allow_poly)
+ {
+ elem_typeid = ANYELEMENTOID;
+ array_typeid = ANYARRAYOID;
+ range_typeid = ANYRANGEOID;
+ }
+ else
+ {
+ /*
+ * Only way to get here is if all the polymorphic args have
+ * UNKNOWN inputs
+ */
+ ereport(ERROR,
+ (errcode(ERRCODE_DATATYPE_MISMATCH),
+ errmsg("could not determine polymorphic type because input has type %s",
+ "unknown")));
+ }
}
- }
- if (!OidIsValid(elem_typeid))
- {
- if (allow_poly)
+ if (have_anynonarray && elem_typeid != ANYELEMENTOID)
{
- elem_typeid = ANYELEMENTOID;
- array_typeid = ANYARRAYOID;
- range_typeid = ANYRANGEOID;
+ /*
+ * require the element type to not be an array or domain over
+ * array
+ */
+ if (type_is_array_domain(elem_typeid))
+ ereport(ERROR,
+ (errcode(ERRCODE_DATATYPE_MISMATCH),
+ errmsg("type matched to anynonarray is an array type: %s",
+ format_type_be(elem_typeid))));
}
- else
+
+ if (have_anyenum && elem_typeid != ANYELEMENTOID)
{
- /* Only way to get here is if all the generic args are UNKNOWN */
- ereport(ERROR,
- (errcode(ERRCODE_DATATYPE_MISMATCH),
- errmsg("could not determine polymorphic type because input has type %s",
- "unknown")));
+ /* require the element type to be an enum */
+ if (!type_is_enum(elem_typeid))
+ ereport(ERROR,
+ (errcode(ERRCODE_DATATYPE_MISMATCH),
+ errmsg("type matched to anyenum is not an enum type: %s",
+ format_type_be(elem_typeid))));
}
}
- if (have_anynonarray && elem_typeid != ANYELEMENTOID)
- {
- /* require the element type to not be an array or domain over array */
- if (type_is_array_domain(elem_typeid))
- ereport(ERROR,
- (errcode(ERRCODE_DATATYPE_MISMATCH),
- errmsg("type matched to anynonarray is an array type: %s",
- format_type_be(elem_typeid))));
- }
-
- if (have_anyenum && elem_typeid != ANYELEMENTOID)
- {
- /* require the element type to be an enum */
- if (!type_is_enum(elem_typeid))
- ereport(ERROR,
- (errcode(ERRCODE_DATATYPE_MISMATCH),
- errmsg("type matched to anyenum is not an enum type: %s",
- format_type_be(elem_typeid))));
- }
-
/*
- * If we had any unknown inputs, re-scan to assign correct types
+ * If we had any UNKNOWN inputs for polymorphic arguments, re-scan to
+ * assign correct types to them.
*/
- if (have_unknowns)
+ if (have_poly_unknowns)
{
- for (j = 0; j < nargs; j++)
+ for (int j = 0; j < nargs; j++)
{
Oid decl_type = declared_arg_types[j];
Oid actual_type = actual_arg_types[j];
}
}
+ /* if we return ANYELEMENT use the appropriate argument type */
+ if (rettype == ANYELEMENTOID ||
+ rettype == ANYNONARRAYOID ||
+ rettype == ANYENUMOID)
+ return elem_typeid;
+
/* if we return ANYARRAY use the appropriate argument type */
if (rettype == ANYARRAYOID)
{
return range_typeid;
}
- /* if we return ANYELEMENT use the appropriate argument type */
- if (rettype == ANYELEMENTOID ||
- rettype == ANYNONARRAYOID ||
- rettype == ANYENUMOID)
- return elem_typeid;
-
/* we don't return a generic type; send back the original return type */
return rettype;
}
index 731db2c77603ce159e25935bd2ca21ed80699ef2..f94ae10e009c698987d9bf307b6a0eba8cec8b6b 100644 (file)
(1 row)
select f1(stavalues1) from pg_statistic; -- fail, can't infer element type
-ERROR: argument declared anyarray is not an array but type anyarray
+ERROR: cannot determine element type of "anyarray" argument
drop function f1(x anyarray);
create function f1(x anyarray) returns anyarray as $$
begin
diff --git a/src/test/regress/expected/polymorphism.out b/src/test/regress/expected/polymorphism.out
index 20f8c511b93d7a34201d174c514256b0e34df9ad..1271ea4a998020387a2f74e51a79efaf50b9ef3f 100644 (file)
(1 row)
select polyf(stavalues1) from pg_statistic; -- fail, can't infer element type
-ERROR: argument declared anyarray is not an array but type anyarray
+ERROR: cannot determine element type of "anyarray" argument
drop function polyf(x anyarray);
create function polyf(x anyarray) returns anyarray as $$
select x