aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorAmit Langote <amitlan@postgresql.org>2024-07-17 17:10:57 +0900
committerAmit Langote <amitlan@postgresql.org>2024-07-17 17:13:48 +0900
commit2177306a64137f50158d0d1ce7c4196ff8f05350 (patch)
tree23323dceb3e3f34c51c59d6395183bf8bde7633a /contrib/postgres_fdw/postgres_fdw.c
parentb4da732fd64e936970f38c792f8b32c4bdf2bcd5 (diff)
downloadpostgresql-2177306a64137f50158d0d1ce7c4196ff8f05350.tar.gz
postgresql-2177306a64137f50158d0d1ce7c4196ff8f05350.zip
SQL/JSON: Rethink c2d93c3802b
This essentially reverts c2d93c3802b except tests. The problem with c2d93c3802b was that it only changed the casting behavior for types with typmod, and had coding issues noted in the post-commit review. This commit changes coerceJsonFuncExpr() to use assignment-level casts instead of explicit casts to coerce the result of JSON constructor functions to the specified or the default RETURNING type. Using assignment-level casts fixes the problem that using explicit casts was leading to the wrong typmod / length coercion behavior -- truncating results longer than the specified length instead of erroring out -- which c2d93c3802b aimed to solve. That restricts the set of allowed target types to string types, the same set that's currently allowed. Discussion: https://postgr.es/m/202406291824.reofujy7xdj3@alvherre.pgsql
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions