database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-12 21:01:52 +03:00
Code Activity

Remove an unnecessary HOLD_INTERRUPTS/RESUME_INTERRUPTS pair.

Browse Source 
This was required back when RESUME_INTERRUPTS could actually
execute ProcessInterrupts, but that hasn't been true since 2001...
This commit is contained in:
Tom Lane
2006-10-22 20:34:54 +00:00
parent bd95c74985
commit 954c1813ac
1 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/backend/storage/buffer/bufmgr.c
View File

@ -8,7 +8,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/storage/buffer/bufmgr.c,v 1.212 2006/10/04 00:29:57 momjian Exp $ * $PostgreSQL: pgsql/src/backend/storage/buffer/bufmgr.c,v 1.213 2006/10/22 20:34:54 tgl Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
@ -694,21 +694,14 @@ retry:
BufTableDelete(&oldTag, oldHash); BufTableDelete(&oldTag, oldHash);
/* /*
* Avoid accepting a cancel interrupt when we release the mapping lock; * Done with mapping lock.
* that would leave the buffer free but not on the freelist. (Which would
* not be fatal, since it'd get picked up again by the clock scanning
* code, but we'd rather be sure it gets to the freelist.)
*/ */
HOLD_INTERRUPTS();
LWLockRelease(oldPartitionLock); LWLockRelease(oldPartitionLock);
/* /*
* Insert the buffer at the head of the list of free buffers. * Insert the buffer at the head of the list of free buffers.
*/ */
StrategyFreeBuffer(buf, true); StrategyFreeBuffer(buf, true);
RESUME_INTERRUPTS();
} }
/* /*