lora-ruby 0.18.0-aarch64-linux → 0.19.0-aarch64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6ec63db25461db026891b772430c487f3fdfc5978b358dade99e940786c11a08
-  data.tar.gz: dd8bf7bcc0a098325164057280275db610175d12b1adf44d721c5570384ca20a
+  metadata.gz: f6c806bdf150dd08b8ecb946669a7923f991d93c1e3b1de4ef098d690a445b46
+  data.tar.gz: 321efb37f096100f59f04c5189f3157f485769389837c9bd6aceaee768aa47c8
 SHA512:
-  metadata.gz: a6a6101d171142d52fb86d4d45e8f0fd89b40d31a7b4d6ece4da5fc1f3879637ac9c0a56a5d4d7c45abbc8a3559fa742b23186e39d347c7840c1edbc673e5a14
-  data.tar.gz: 4c243502aa627aca54283fb2177b81d20e84661f90b62e43c0f1e2eb1d4c7edbe7368cd71c1d78fecac7abcb7919dd40df8fd1c05e4efbc17732f7c2e4d22169
+  metadata.gz: 753d7229175ea205b0346766de4b55afedd3c994dfafcf31447e3c0344f8f2052562adf52a4c32e27288ac3e1914320f8f15b032fe1021284ec8ed6a1e72c8fe
+  data.tar.gz: 4c981e6cf63f163eaf36a99ac2b1e6c64250ddd0e41e990b8b86b5f014951adcfecec8f72c1756c8d1bbb56faf18824431a44ce717153c77481d462076d35b53

data/README.md

@@ -206,14 +206,24 @@ db = LoraRuby::Database.open_wal(
 
 ## Concurrency (GVL release)
 
-`Database#execute` calls `rb_thread_call_without_gvl`, so other Ruby
-threads run while the engine is busy. Auto-commit reads can overlap on engine
-snapshots; write commits and explicit read-write transactions serialize.
+Every engine call that can block (`execute`, `explain`, `profile`, `clear`,
+snapshot save/load, opening and closing a database) runs under
+`rb_thread_call_without_gvl`, so other Ruby threads run while the engine is
+busy. `node_count` and `relationship_count` read a snapshot without waiting
+and keep the GVL. Auto-commit reads can overlap on engine snapshots; writes
+serialize on the engine's writer lock.
+
+A write waiting for that lock waits with the GVL released, and the Ruby
+binding has no interactive transactions: each write takes the lock and
+releases it within one call. So a waiting writer never blocks the writer
+holding the lock, however many threads write at once.
 
 The engine has no cancellation hook, so we pass a `NULL` unblock
-function. A thread interrupted mid-query (`Thread#kill`) will observe
-the interrupt **after** the current query finishes. Keep queries short
-if you rely on cooperative cancellation.
+function. A thread interrupted mid-query (`Thread#kill`, `Ctrl-C`) will
+observe the interrupt **after** the current call finishes, including a
+write that was still waiting for the writer lock (it runs, then the
+interrupt fires). Keep queries short if you rely on cooperative
+cancellation.
 
 ## Local development
 

data/lib/lora_ruby/version.rb

@@ -10,5 +10,5 @@ module LoraRuby
   # Guard against redefinition so re-requiring this file (or loading
   # both paths) doesn't emit a "warning: already initialized constant"
   # when the native extension loads second with the identical value.
-  VERSION = "0.18.0" unless const_defined?(:VERSION)
+  VERSION = "0.19.0" unless const_defined?(:VERSION)
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: lora-ruby
 version: !ruby/object:Gem::Version
-  version: 0.18.0
+  version: 0.19.0
 platform: aarch64-linux
 authors:
 - LoraDB, Inc.