pg_eventstore 3.0.0 → 3.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4425f2f4cffd24b06156465726034e4c8da383fed7f0576837851a65390068e0
-  data.tar.gz: bb809d708eaea98368d54bae14a8d35f36265a7a5ad66c4b8fd9b5dc57293163
+  metadata.gz: 24899ca6d10bac21341f41f3a8cfee09e10ce10bf81fb4525e9660f6c708d3af
+  data.tar.gz: 07cbbca86a3cb488d9123d663e77cb66cdbf850f93e12f1f15e46dc8f465879c
 SHA512:
-  metadata.gz: e86a98610d16b95eeb4bffa5a3b0d74055ac7901a30f20d297aee1b37786e06f94ff483c135f99df255cd23f50b3cac4d9360c6338ccbdab7d58d14b05fc5578
-  data.tar.gz: cdfe9c6093814265d91905f1405ff39bbd347a4e844c75961f3b3db56eb0fb4f32537b4cd26a0bb7c46b82abb21d25cb2aa7831623466cd3e2a3d5d50caf4a42
+  metadata.gz: bc33cc4bcdda545ffa4476e80b55ca2541de4da036d715644f3957d1889170bbdf3b05b1391c7f981f28163da0ce36d06b0a8282ddeddb7560eb1892df43cfaa
+  data.tar.gz: 64b63413791d2c993315d4012acb1a5bec19b237eae6761c6b9da8725483e4284f5fbf3b956df5c4a750719460087f30cec6c9db1f176ce728ad985f2aefa213

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 ## [Unreleased]
 
+## [3.0.1]
+
+- Fix EventTracing bug: Respect user-supplied Event#correlation_id value when caused_by#correlation_id is absent
+
 ## [3.0.0]
 
 - New feature: pg_eventstore replication

data/README.md

@@ -12,6 +12,8 @@ Implements database and API to store and read events in event sourced systems.
 
 ### Migrating to v3
 
+v3 introduces several new tables to support the functional. Make sure you have enough disk space on your PostgreSQL host.
+
 If you are migrating from v2 - please don't forget to delete cron jobs and `pg_cron` extension after migration to v3.
 You can remove cron jobs as follows:
 

data/docs/configuration.md

@@ -154,3 +154,32 @@ split your replica subscriptions from your application subscriptions and adjust
 Please note, that this is an **upper limit** of events to replicate at a time. Subscriptions have their own measurement
 of how many events a subscription handler processes per second. Thus, the number of events actually processed by a
 subscription at a time may differ.
+
+## PostgreSQL settings
+
+If you are running PostgreSQL from docker - make sure you adjust `shm_size` docker setting from its default (`/dev/shm`
+size; responsible for the shared memory size; default is `64M`) so that parallel PostgreSQL workers have enough
+resources.
+
+The more partitions you have, the more locks are required for operations that affect multiple partitions. It mainly
+concerns the case when you involve many different event types when using `Client#multiple`. It may lead to the next
+error:
+
+```
+ERROR:  out of shared memory (PG::OutOfMemory)
+HINT:  You might need to increase max_pred_locks_per_transaction.
+```
+
+PostgreSQL suggests to increase the `max_pred_locks_per_transaction`(the description of it
+is [here](https://www.postgresql.org/docs/current/runtime-config-locks.html)). The default value is `64`. In case you
+have several thousands of partitions - you may want to set it to `128` or even to `256`.
+
+You may also face similar error which refers to `max_locks_per_transaction` setting:
+
+```
+PG::OutOfMemory: ERROR:  out of shared memory (PG::OutOfMemory)
+HINT:  You might need to increase "max_locks_per_transaction".
+```
+
+The reason of it to appear is the same - too many objects(partition tables, indexes, etc) are involved in a single
+transaction.

data/docs/how_it_works.md

@@ -51,31 +51,6 @@ end.to_a
 #    {"id"=>3, "context"=>"SomeCtx", "stream_name"=>"SomeStream", "event_type"=>"SomethingChanged", "table_name"=>"event_types_aeadd5"}]
 ```
 
-### PostgreSQL settings
-
-The more partitions you have, the more locks are required for operations that affect multiple partitions. It mainly
-concerns the case when you involve many different event types when using `Client#multiple`. It may lead to the next
-error:
-
-```
-ERROR:  out of shared memory (PG::OutOfMemory)
-HINT:  You might need to increase max_pred_locks_per_transaction.
-```
-
-PostgreSQL suggests to increase the `max_pred_locks_per_transaction`(the description of it
-is [here](https://www.postgresql.org/docs/current/runtime-config-locks.html)). The default value is `64`. In case you
-have several thousands of partitions - you may want to set it to `128` or even to `256`.
-
-You may also face similar error which refers to `max_locks_per_transaction` setting:
-
-```
-PG::OutOfMemory: ERROR:  out of shared memory (PG::OutOfMemory)
-HINT:  You might need to increase "max_locks_per_transaction".
-```
-
-The reason of it to appear is the same - too many objects(partition tables, indexes, etc) are involved in a single
-transaction.
-
 ## Appending events and multiple commands
 
 You may want to get familiar with [Appending events](appending_events.md) and [multiple commands](multiple_commands.md)

data/lib/pg_eventstore/middleware/event_tracing.rb

@@ -31,7 +31,7 @@ module PgEventstore
           event.feature_markers.push(self.class.causation_marker(event.causation_id))
         end
 
-        event.correlation_id = event.caused_by&.correlation_id&.dup || SecureRandom.uuid_v7
+        event.correlation_id = event.caused_by&.correlation_id&.dup || event.correlation_id || SecureRandom.uuid_v7
         event.metadata[CORRELATION_ID_KEY] = event.correlation_id
         event.feature_markers.push(self.class.correlation_marker(event.correlation_id))
       end

data/lib/pg_eventstore/version.rb

@@ -2,5 +2,5 @@
 
 module PgEventstore
   # @return [String]
-  VERSION = '3.0.0'
+  VERSION = '3.0.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pg_eventstore
 version: !ruby/object:Gem::Version
-  version: 3.0.0
+  version: 3.0.1
 platform: ruby
 authors:
 - Ivan Dzyzenko