Skip to content

Commit 98040f6

Browse files
Remove a couple of sentences that may be slightly misleading now
...that we've concluded we cannot use dirty deletes in at least some areas. The sentence left is pretty to the point.
1 parent 495ead3 commit 98040f6

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

src/rabbit_binding.erl

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -444,10 +444,7 @@ remove_for_destination(DstName, OnlyDurable, Fun) ->
444444
lists:keysort(#binding.source, Bindings), OnlyDurable).
445445

446446
%% Instead of locking entire table on remove operations we can lock the
447-
%% affected resource only. This will allow us to use dirty_match_object for
448-
%% do faster search of records to delete.
449-
%% This works better when there are multiple resources deleted at once, for
450-
%% example when exclusive queues are deleted.
447+
%% affected resource only.
451448
lock_resource(Name) ->
452449
mnesia:lock({global, Name, mnesia:table_info(rabbit_route, where_to_write)},
453450
write).

0 commit comments

Comments
 (0)