You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unique job insertion takes a Postgres advisory lock to make sure that its uniqueness check still works even if two conflicting insert operations are occurring in parallel. Postgres advisory locks share a global 64-bit namespace, which is a large enough space that it's unlikely for two advisory locks to ever conflict, but to _guarantee_ that River's advisory locks never interfere with an application's, River can be configured with a 32-bit advisory lock prefix which it will use for all its locks:
Doing so has the downside of leaving only 32 bits for River's locks (64 bits total - 32-bit prefix), making them somewhat more likely to conflict with each other.
@@ -111,17 +111,17 @@ Use `#insert_many` to bulk insert jobs as a single operation for improved effici
111
111
112
112
```python
113
113
num_inserted = client.insert_many([
114
-
SimpleArgs(job_num: 1),
115
-
SimpleArgs(job_num: 2)
114
+
SimpleArgs(job_num=1),
115
+
SimpleArgs(job_num=2)
116
116
])
117
117
```
118
118
119
119
Or with `InsertManyParams`, which may include insertion options:
0 commit comments