summaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorPeter Eisentraut2018-10-09 10:04:04 +0000
committerPeter Eisentraut2018-10-15 08:34:35 +0000
commit5b75a4f8266a4f187a47929fed0582ee778c703f (patch)
tree990d1f511957821efd3fb18f5efdeb9f9d444c39 /src/backend/executor/nodeModifyTable.c
parent35584fd05f9b104f057c700360985991f111a847 (diff)
pgbench: Report errors during run better
When an error occurs during a benchmark run, exit with a nonzero exit code and write a message at the end. Previously, it would just print the error message when it happened but then proceed to print the run summary normally and exit with status 0. To still allow distinguishing setup from run-time errors, we use exit status 2 for the new state, whereas existing errors during pgbench initialization use exit status 1. Reviewed-by: Fabien COELHO <[email protected]>
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions