Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commite3db3f8

Browse files
committed
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 beonly an issue within EmitErrorReport(), where the elog hook is forexample called. That's unlikely to going to be a problem, but let's beclean and consistent with other code paths handling exceptions. This ispresent since2909419, which introduced autovacuum.Author: Ashwin AgrawalReviewed-by: Tom Lane, Michael PaquierDiscussion:https://postgr.es/m/CALfoeisM+_+dgmAdAOHAu0k-ZpEHHqSSG=GRf3pKJGm8OqWX0w@mail.gmail.comBackpatch-through: 9.4
1 parentad4b7ae commite3db3f8

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

‎src/backend/postmaster/autovacuum.c

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1558,6 +1558,9 @@ AutoVacWorkerMain(int argc, char *argv[])
15581558
*/
15591559
if (sigsetjmp(local_sigjmp_buf,1)!=0)
15601560
{
1561+
/* since not using PG_TRY, must reset error stack by hand */
1562+
error_context_stack=NULL;
1563+
15611564
/* Prevents interrupts while cleaning up */
15621565
HOLD_INTERRUPTS();
15631566

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp