aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parser.c
diff options
context:
space:
mode:
authorDean Rasheed <dean.a.rasheed@gmail.com>2023-02-22 13:28:30 +0000
committerDean Rasheed <dean.a.rasheed@gmail.com>2023-02-22 13:28:30 +0000
commit52dbd9f845987ff3a6f97d30b3bebb13fdb4b2b4 (patch)
tree68f7175dc9bffd3e631c37a7779e459eafecbb96 /src/backend/parser/parser.c
parent463bef38332efaef39de22e4325688924a934b76 (diff)
downloadpostgresql-52dbd9f845987ff3a6f97d30b3bebb13fdb4b2b4.tar.gz
postgresql-52dbd9f845987ff3a6f97d30b3bebb13fdb4b2b4.zip
Add missing support for the latest SPI status codes.
SPI_result_code_string() was missing support for SPI_OK_TD_REGISTER, and in v15 and later, it was missing support for SPI_OK_MERGE, as was pltcl_process_SPI_result(). The last of those would trigger an error if a MERGE was executed from PL/Tcl. The others seem fairly innocuous, but worth fixing. Back-patch to all supported branches. Before v15, this is just adding SPI_OK_TD_REGISTER to SPI_result_code_string(), which is unlikely to be seen by anyone, but seems worth doing for completeness. Reviewed by Tom Lane. Discussion: https://postgr.es/m/CAEZATCUg8V%2BK%2BGcafOPqymxk84Y_prXgfe64PDoopjLFH6Z0Aw%40mail.gmail.com https://postgr.es/m/CAEZATCUMe%2B_KedPMM9AxKqm%3DSZogSxjUcrMe%2BsakusZh3BFcQw%40mail.gmail.com
Diffstat (limited to 'src/backend/parser/parser.c')
0 files changed, 0 insertions, 0 deletions