diff options
| author | Michael Klishin <michael@clojurewerkz.org> | 2018-08-30 19:56:52 +0300 |
|---|---|---|
| committer | Michael Klishin <michael@clojurewerkz.org> | 2018-08-30 19:56:52 +0300 |
| commit | 98040f6e8b9142baae025cf904289e61d7e6d7af (patch) | |
| tree | b0ea7c1a7da664dd4f466e80426f69ed7ebb2d80 /src | |
| parent | 495ead38956b2d1bcde5db071118ca4b50ab2812 (diff) | |
| download | rabbitmq-server-git-98040f6e8b9142baae025cf904289e61d7e6d7af.tar.gz | |
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.
Diffstat (limited to 'src')
| -rw-r--r-- | src/rabbit_binding.erl | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/src/rabbit_binding.erl b/src/rabbit_binding.erl index e01ca060a9..f2bcd93b74 100644 --- a/src/rabbit_binding.erl +++ b/src/rabbit_binding.erl @@ -444,10 +444,7 @@ remove_for_destination(DstName, OnlyDurable, Fun) -> lists:keysort(#binding.source, Bindings), OnlyDurable). %% Instead of locking entire table on remove operations we can lock the -%% affected resource only. This will allow us to use dirty_match_object for -%% do faster search of records to delete. -%% This works better when there are multiple resources deleted at once, for -%% example when exclusive queues are deleted. +%% affected resource only. lock_resource(Name) -> mnesia:lock({global, Name, mnesia:table_info(rabbit_route, where_to_write)}, write). |