| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | james(dot)inform(at)pharmapp(dot)de, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD) |
| Date: | 2022-01-28 20:28:10 |
| Message-ID: | CAFj8pRDMMTXX1B56P=7cvJvDSOYuhrVE_PBch7EFOV8-qOHNzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
pá 28. 1. 2022 v 21:19 odesílatel Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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
>>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-01-28 21:43:18 | Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD) |
| Previous Message | Pavel Stehule | 2022-01-28 20:19:57 | Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD) |