diff options
| author | Michael Paquier | 2019-05-09 01:30:08 +0000 |
|---|---|---|
| committer | Michael Paquier | 2019-05-09 01:30:08 +0000 |
| commit | a475b1e77e13ce282603e4133c7cbcbd537d508c (patch) | |
| tree | d08cde91591767ec16944bb7b2842ad6838b031a | |
| parent | 2be2fee248396bbfdeced55f74fd23148e2745af (diff) | |
Fix error status of vacuumdb when multiple jobs are used
When running a batch of VACUUM or ANALYZE commands on a given database,
there were cases where it is possible to have vacuumdb not report an
error where it actually should, leading to incorrect status results.
Author: Julien Rouhaud
Reviewed-by: Amit Kapila, Michael Paquier
Discussion: https://postgr.es/m/CAOBaU_ZuTwz7CtqLYJ1Ouuh272bTQPLN8b1bAPk0bCBm4PDMTQ@mail.gmail.com
Backpatch-through: 9.5
| -rw-r--r-- | src/bin/scripts/vacuumdb.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/bin/scripts/vacuumdb.c b/src/bin/scripts/vacuumdb.c index a5fcd30478d..b6f30030e99 100644 --- a/src/bin/scripts/vacuumdb.c +++ b/src/bin/scripts/vacuumdb.c @@ -518,7 +518,10 @@ vacuum_one_database(const char *dbname, vacuumingOptions *vacopts, for (j = 0; j < concurrentCons; j++) { if (!GetQueryResult((slots + j)->connection, progname)) + { + failed = true; goto finish; + } } } |