Resolve untyped parameters in FOR PORTION OF FROM/TO bounds FOR PORTION OF valid_at FROM $1 TO $2 fails with "could not determine data type of parameter $1", so using PREPARE requires users to say $1::date etc. But transformForPortionOfClause() already coerces the bounds, since it builds a constructor for the targeted range. We just need to store the coerced expressions in targetFrom and targetTo.
This also improves pg_get_ruledef(), which now renders an untyped NULL bound as NULL::date instead of NULL::unknown. Reported-by: Noah Misch <[email protected]> Author: Paul A. Jungwirth <[email protected]> Discussion: https://www.postgresql.org/message-id/flat/CA%2BrenyW1uJp1dw%3DiK7MsWfbbZf-dKP_4JLoQ65wj%3Dfry35FjCw%40mail.gmail.com Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/f1940321687644a3ef38dccca8bbeb7c50d4cbdc Modified Files -------------- src/backend/parser/analyze.c | 12 ++- src/test/regress/expected/for_portion_of.out | 106 ++++++++++++++++++++++++++- src/test/regress/sql/for_portion_of.sql | 71 ++++++++++++++++++ 3 files changed, 185 insertions(+), 4 deletions(-)
