diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2018-10-09 12:04:04 +0200 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2018-10-15 10:34:35 +0200 |
| commit | 5b75a4f8266a4f187a47929fed0582ee778c703f (patch) | |
| tree | 990d1f511957821efd3fb18f5efdeb9f9d444c39 /src/backend/executor | |
| parent | 35584fd05f9b104f057c700360985991f111a847 (diff) | |
| download | postgresql-5b75a4f8266a4f187a47929fed0582ee778c703f.tar.gz postgresql-5b75a4f8266a4f187a47929fed0582ee778c703f.zip | |
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 <coelho@cri.ensmp.fr>
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions