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

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:19:57
Message-ID: CAFj8pRCdDOs9w-u7x2LHoN-uUVOQqj4SH+VfBWA9BCHBDpckgw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Regards

Pavel Stehule

> Cheers,
> James
>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2022-01-28 20:28:10 Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
Previous Message PG Bug reporting form 2022-01-28 17:22:06 BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)