aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2019-05-09 10:29:10 +0900
committerMichael Paquier <michael@paquier.xyz>2019-05-09 10:29:10 +0900
commit3ae3c18b362817f9412c380539f1a16c7abb79c9 (patch)
tree849c9f11346e8b650ec7bc5d1f70c81fd4f307e4 /contrib/postgres_fdw/postgres_fdw.c
parentd95e36dc384e3068ae2db909c228b1800737b18d (diff)
downloadpostgresql-3ae3c18b362817f9412c380539f1a16c7abb79c9.tar.gz
postgresql-3ae3c18b362817f9412c380539f1a16c7abb79c9.zip
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
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions