mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Hold interrupts while running dsm_detach() callbacks.

Browse Source 
While cleaning up after a parallel query or parallel index creation that
created temporary files, we could be interrupted by a statement timeout.
The error handling path would then fail to clean up the files when it
ran dsm_detach() again, because the callback was already popped off the
list.  Prevent this hazard by holding interrupts while the cleanup code
runs.

Thanks to Heikki Linnakangas for this suggestion, and also to Kyotaro
Horiguchi, Masahiko Sawada, Justin Pryzby and Tom Lane for discussion of
this and earlier ideas on how to fix the problem.

Back-patch to all supported releases.

Reported-by: Justin Pryzby <pryzby@telsasoft.com>
Discussion: https://postgr.es/m/20191212180506.GR2082@telsasoft.com
This commit is contained in:
Thomas Munro 2021-02-15 13:32:58 +13:00
parent 2200168462
commit acafdd9ed5
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/backend/storage/ipc/dsm.c
View File

@ -707,8 +707,12 @@ dsm_detach(dsm_segment *seg)
/*
* Invoke registered callbacks. Just in case one of those callbacks
* throws a further error that brings us back here, pop the callback
* before invoking it, to avoid infinite error recursion.
* before invoking it, to avoid infinite error recursion. Don't allow
* interrupts while running the individual callbacks in non-error code
* paths, to avoid leaving cleanup work unfinished if we're interrupted by
* a statement timeout or similar.
*/
HOLD_INTERRUPTS();
while (!slist_is_empty(&seg->on_detach))
{
slist_node *node;
@ -724,6 +728,7 @@ dsm_detach(dsm_segment *seg)
function(seg, arg);
}
RESUME_INTERRUPTS();
/*
* Try to remove the mapping, if one exists. Normally, there will be, but