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

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
Дата
Msg-id CAFj8pRDMMTXX1B56P=7cvJvDSOYuhrVE_PBch7EFOV8-qOHNzQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #17387: Working in PG13 but not in PGH14: array_agg(RECORD)