Treat JsonConstructorExpr as non-strict JsonConstructorExpr can produce non-NULL output with a NULL input, so it should be treated as a non-strict construct. Failing to do so can lead to incorrect query behavior.
For example, in the reported case, when pulling up a subquery that is under an outer join, if the subquery's target list contains a JsonConstructorExpr that uses subquery variables and it is mistakenly treated as strict, it will be pulled up without being wrapped in a PlaceHolderVar. As a result, the expression will be evaluated at the wrong place and will not be forced to null when the outer join should do so. Back-patch to v16 where JsonConstructorExpr was introduced. Bug: #19046 Reported-by: Runyuan He <runy...@berkeley.edu> Author: Tender Wang <tndrw...@gmail.com> Co-authored-by: Richard Guo <guofengli...@gmail.com> Discussion: https://postgr.es/m/19046-765b6602b0a8c...@postgresql.org Backpatch-through: 16 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/b63a822452152a7bd613fd4b28e0967e626e274e Modified Files -------------- src/backend/optimizer/util/clauses.c | 2 ++ src/test/regress/expected/subselect.out | 28 ++++++++++++++++++++++++++++ src/test/regress/sql/subselect.sql | 17 +++++++++++++++++ 3 files changed, 47 insertions(+)
