Commit1fe0466

committed

Fix comment in LockReleaseAll() on when locallock->nLock can be zero

We reach this case also e.g. when a deadlock is detected, not onlywhen we run out of memory.Reviewed-by: Maxim OrlovDiscussion:https://www.postgresql.org/message-id/7c2090cd-a72a-4e34-afaa-6dd2ef31440e@iki.fi

1 parent99b937a commit1fe0466Copy full SHA for 1fe0466

File tree

-3

lines changed

-3

lines changed

Lines changed: 2 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -2258,9 +2258,8 @@ LockReleaseAll(LOCKMETHODID lockmethodid, bool allLocks)`
`2258`	`2258`	`while ((locallock= (LOCALLOCK*)hash_seq_search(&status))!=NULL)`
`2259`	`2259`	`{`
`2260`	`2260`	`/*`
`2261`		`- * If the LOCALLOCK entry is unused, we must've run out of shared`
`2262`		`- * memory while trying to set up this lock. Just forget the local`
`2263`		`- * entry.`
	`2261`	`+ * If the LOCALLOCK entry is unused, something must've gone wrong`
	`2262`	`+ * while trying to acquire this lock. Just forget the local entry.`
`2264`	`2263`	`*/`
`2265`	`2264`	`if (locallock->nLocks==0)`
`2266`	`2265`	`{`

Comments

(0)