Clean up properly error_context_stack in autovacuum worker on exception
authorMichael Paquier <[email protected]>
Wed, 23 Oct 2019 01:26:23 +0000 (10:26 +0900)
committerMichael Paquier <[email protected]>
Wed, 23 Oct 2019 01:26:23 +0000 (10:26 +0900)
commitebf7b2e01bd960d55e5a186855feecd6f68460fd
treeea07471e175d85c8e69e152c3de46b81a5fa6a70
parente3267407e2f9c30b6c94da25da8ba078dc144702
Clean up properly error_context_stack in autovacuum worker on exception

Any callback set would have no meaning in the context of an exception.
As an autovacuum worker exits quickly in this context, this could be
only an issue within EmitErrorReport(), where the elog hook is for
example called.  That's unlikely to going to be a problem, but let's be
clean and consistent with other code paths handling exceptions.  This is
present since 2909419, which introduced autovacuum.

Author: Ashwin Agrawal
Reviewed-by: Tom Lane, Michael Paquier
Discussion: https://postgr.es/m/CALfoeisM+_+dgmAdAOHAu0k-ZpEHHqSSG=GRf3pKJGm8OqWX0w@mail.gmail.com
Backpatch-through: 9.4
src/backend/postmaster/autovacuum.c