Provide an error cursor for "can't subscript" error messages.
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 11 Dec 2020 22:54:10 +0000 (17:54 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 11 Dec 2020 23:58:21 +0000 (18:58 -0500)
commit653aa603f501aa6e4865105a928cd13082ee7152
tree158acf06d799a63fa44fc83e9800a3896ad66255
parentd2a2808eb444986d2fe716a48e21993329142f3d
Provide an error cursor for "can't subscript" error messages.

Commit c7aba7c14 didn't add this, but after more fooling with the
feature I feel that it'd be useful.  To make this possible, refactor
getSubscriptingRoutines() so that the caller is responsible for
throwing any error.  (In clauses.c, I just chose to make the
most conservative assumption rather than throwing an error.  We don't
expect failures there anyway really, so the code space for an error
message would be a poor investment.)
src/backend/executor/execExpr.c
src/backend/optimizer/util/clauses.c
src/backend/parser/parse_node.c
src/backend/utils/cache/lsyscache.c
src/test/regress/expected/arrays.out