]> granicus.if.org Git - postgresql/commit
Fix autovacuum launcher shutdown sequence
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Wed, 8 Apr 2015 16:19:49 +0000 (13:19 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Wed, 8 Apr 2015 16:19:49 +0000 (13:19 -0300)
commitcf5d3f27484177cc4a44ec2bcdd786c9b8e59746
tree69417eeb0e7e68e4f5b7cb0663efacc14df4858b
parentc68b06356dd75230df18a763b87736f717e13b5c
Fix autovacuum launcher shutdown sequence

It was previously possible to have the launcher re-execute its main loop
before shutting down if some other signal was received or an error
occurred after getting SIGTERM, as reported by Qingqing Zhou.

While investigating, Tom Lane further noticed that if autovacuum had
been disabled in the config file, it would misbehave by trying to start
a new worker instead of bailing out immediately -- it would consider
itself as invoked in emergency mode.

Fix both problems by checking the shutdown flag in a few more places.
These problems have existed since autovacuum was introduced, so
backpatch all the way back.
src/backend/postmaster/autovacuum.c