Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Fix Version/s: 10.1.3
-
Component/s: Replication
-
Labels:
Description
pool->threads is freed before being reassigned the new pool.
Although not really a memory barrier I though it prudent to keep the pool thread count to be the lower of the old/new thread list before the new threads is allocated.
Patch refers
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Hm. As you say, due to no barriers this doesn't actually make any semantic
change. But ok, if you think it makes the code clearer, it doesn't hurt
anything, so I'll push it to 10.1.