Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD) - Mailing list pgsql-bugs

From Pavel Stehule
Subject Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
Date
Msg-id CAFj8pRDMMTXX1B56P=7cvJvDSOYuhrVE_PBch7EFOV8-qOHNzQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view


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

pgsql-bugs by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
Next
From: Tom Lane
Date:
Subject: Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)