Issue 9264 - Add lock to slapo-unique to delay new ops until current op is complete
Summary: Add lock to slapo-unique to delay new ops until current op is complete
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: overlays (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: 2.5.0
Assignee: OpenLDAP project
URL:
Keywords:
: 5908 (view as issue list)
Depends on:
Blocks:
 
Reported: 2020-05-21 17:42 UTC by gnoe@symas.com
Modified: 2020-10-14 21:23 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description gnoe@symas.com 2020-05-21 17:42:43 UTC 
Locking is needed in slapo-unique to prevent duplicate values when new operations are started before previous operations are completed.
Comment 1 Quanah Gibson-Mount 2020-05-21 17:45:51 UTC 
I would hope you mean only write ops... It'd be terrible to block read operations.
Comment 2 Quanah Gibson-Mount 2020-05-22 15:37:57 UTC 
Commits: 
  • 9183abe6 
by Howard Chu at 2020-05-22T15:08:20+01:00 
ITS#9264 add an optional lock to slapo-unique
Comment 3 Quanah Gibson-Mount 2020-05-25 22:46:23 UTC 
Commits: 
  • c70e2e08 
by Howard Chu at 2020-05-25T22:38:30+01:00 
ITS#9264 more for unique locking
Comment 4 Quanah Gibson-Mount 2020-08-28 23:18:13 UTC 
*** Issue 5908 has been marked as a duplicate of this issue. ***