aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeMaterial.c
diff options
context:
space:
mode:
authorDean Rasheed <dean.a.rasheed@gmail.com>2023-02-22 13:27:29 +0000
committerDean Rasheed <dean.a.rasheed@gmail.com>2023-02-22 13:27:29 +0000
commit906356cf6128ac6e35bcb07f7fd5361eb76c4999 (patch)
tree1d641b1d44755f7296ebc2e5ef5eca75d779b5e2 /src/backend/executor/nodeMaterial.c
parent99e74cd235a5cb7d58eadfc627e4e1b1ebac1231 (diff)
downloadpostgresql-906356cf6128ac6e35bcb07f7fd5361eb76c4999.tar.gz
postgresql-906356cf6128ac6e35bcb07f7fd5361eb76c4999.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/executor/nodeMaterial.c')
0 files changed, 0 insertions, 0 deletions