Horton

Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)

Pavel Stehule <pavel.stehule@gmail.com>

View thread View on postgr.es
From: Pavel Stehule <pavel.stehule@gmail.com>
To: james.inform@pharmapp.de, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-01-28T20:28:10Z
Lists: pgsql-bugs 
pá 28. 1. 2022 v 21:19 odesílatel Pavel Stehule <pavel.stehule@gmail.com>
napsal:

> Hi
>
>
>> Let's not discuss if such an sql makes sense.
>> But question is: Why is PG14 giving an error while PG13 works?
>>
>
> Probably it is side effect of this patch
>
>
> https://github.com/postgres/postgres/commit/9e38c2bb5093ceb0c04d6315ccd8975bd17add66#diff-e2a931f90073b784e341960c6fe1f48aaea4b5d57eb4388143534eec3863477b
>
> The array_append, array_cat, array_prepend changed input types from any*
> kind of polymorphic types to anycompatible* kind of polymorphic types
>

anycompatible* types are less sensitive to different data types, but it
increases a risk of possibility of errors when more than one function can
be detected for execution on analysis of function's signatures.


> Regards
>
> Pavel Stehule
>
>
>
>> Cheers,
>> James
>>
>>

Commits

  1. Fix failure to validate the result of select_common_type().

  2. Declare assorted array functions using anycompatible not anyelement.