diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2005-12-29 18:08:05 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2005-12-29 18:08:05 +0000 |
| commit | 195f1642285d59b4bd42ec2ba8bbcf46b8aedd93 (patch) | |
| tree | 22da2794ecf95bafe907556acaa83ea45ef1042b /src/backend/tcop/postgres.c | |
| parent | e135d9631bcf789ce3aa3a351e2d8af7fc743896 (diff) | |
| download | postgresql-195f1642285d59b4bd42ec2ba8bbcf46b8aedd93.tar.gz postgresql-195f1642285d59b4bd42ec2ba8bbcf46b8aedd93.zip | |
Get rid of the SpinLockAcquire/SpinLockAcquire_NoHoldoff distinction
in favor of having just one set of macros that don't do HOLD/RESUME_INTERRUPTS
(hence, these correspond to the old SpinLockAcquire_NoHoldoff case).
Given our coding rules for spinlock use, there is no reason to allow
CHECK_FOR_INTERRUPTS to be done while holding a spinlock, and also there
is no situation where ImmediateInterruptOK will be true while holding a
spinlock. Therefore doing HOLD/RESUME_INTERRUPTS while taking/releasing a
spinlock is just a waste of cycles. Qingqing Zhou and Tom Lane.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions