Commit96ae658

committed

Move lwlock-release probe back where it belongs

The documentation specifically states that lwlock-release fires beforeany released waiters have been awakened. It worked that way untilab5194e, where is seems to have beenmisplaced 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

1 parent882b2cd commit96ae658Copy full SHA for 96ae658

File tree

-2

lines changed

-2

lines changed

Lines changed: 1 addition & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1840,6 +1840,7 @@ LWLockRelease(LWLock *lock)`
`1840`	`1840`	`/* nobody else can have that kind of lock */`
`1841`	`1841`	`Assert(!(oldstate&LW_VAL_EXCLUSIVE));`
`1842`	`1842`
	`1843`	`+TRACE_POSTGRESQL_LWLOCK_RELEASE(T_NAME(lock));`
`1843`	`1844`
`1844`	`1845`	`/*`
`1845`	`1846`	`* We're still waiting for backends to get scheduled, don't wake them up`
`@@ -1863,8 +1864,6 @@ LWLockRelease(LWLock *lock)`
`1863`	`1864`	`LWLockWakeup(lock);`
`1864`	`1865`	`}`
`1865`	`1866`
`1866`		`-TRACE_POSTGRESQL_LWLOCK_RELEASE(T_NAME(lock));`
`1867`		`-`
`1868`	`1867`	`/*`
`1869`	`1868`	`* Now okay to allow cancel/die interrupts.`
`1870`	`1869`	`*/`

Comments

(0)