diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2021-03-21 08:02:30 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2021-03-21 08:02:30 +0100 |
| commit | 96ae658e6238c5e69819fb1557c2c14a555506d8 (patch) | |
| tree | dd8d5201cf7e8bf32dc832e0acbc299cb9a937e9 /src | |
| parent | 882b2cdc08c4100e273f24742e2118be98708a07 (diff) | |
| download | postgresql-96ae658e6238c5e69819fb1557c2c14a555506d8.tar.gz postgresql-96ae658e6238c5e69819fb1557c2c14a555506d8.zip | |
Move lwlock-release probe back where it belongs
The documentation specifically states that lwlock-release fires before
any released waiters have been awakened. It worked that way until
ab5194e6f617a9a9e7aadb3dd1cee948a42d0755, where is seems to have been
misplaced accidentally. Move it back where it belongs.
Author: Craig Ringer <craig.ringer@enterprisedb.com>
Discussion: https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/storage/lmgr/lwlock.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/src/backend/storage/lmgr/lwlock.c b/src/backend/storage/lmgr/lwlock.c index adf19aba759..975d547f34b 100644 --- a/src/backend/storage/lmgr/lwlock.c +++ b/src/backend/storage/lmgr/lwlock.c @@ -1840,6 +1840,7 @@ LWLockRelease(LWLock *lock) /* nobody else can have that kind of lock */ Assert(!(oldstate & LW_VAL_EXCLUSIVE)); + TRACE_POSTGRESQL_LWLOCK_RELEASE(T_NAME(lock)); /* * We're still waiting for backends to get scheduled, don't wake them up @@ -1863,8 +1864,6 @@ LWLockRelease(LWLock *lock) LWLockWakeup(lock); } - TRACE_POSTGRESQL_LWLOCK_RELEASE(T_NAME(lock)); - /* * Now okay to allow cancel/die interrupts. */ |